Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slim down issue template appearance #7988

Merged
merged 1 commit into from
Mar 14, 2016
Merged

Slim down issue template appearance #7988

merged 1 commit into from
Mar 14, 2016

Conversation

liggitt
Copy link
Contributor

@liggitt liggitt commented Mar 14, 2016

Moves the description to the top so it appears in email summaries
Change to a much smaller header to make actual text more readable

@deads2k
Copy link
Contributor

deads2k commented Mar 14, 2016

Moves the description to the top so it appears in email summaries
Changes headers to bold

Is lack of a template a problem that we've had for the a significant percentage of issues? I noticed issues based on this template this morning and thought that it significantly reduced the readability of the issue itself. Certainly dev-to-dev, this is a waste of time/space.

@liggitt
Copy link
Contributor Author

liggitt commented Mar 14, 2016

I don't know, but this helps readability, imo

@liggitt
Copy link
Contributor Author

liggitt commented Mar 14, 2016

@mfojtik @bparees thoughts?

## Current Result
##### Current Result

...
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we're going to bikeshed, i'd rather not have "..." here since everyone will have to delete it.

(same below)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure

@bparees
Copy link
Contributor

bparees commented Mar 14, 2016

@deads2k is clearly in the @stevekuznetsov camp.

@deads2k you're free to delete the template and go free-form, but for the community coming to us with problems, this helps insure they actually provide the information we need to help them with their problem.

developers should be using bugzilla and trello anyway not issues, since issues are not well integrated into our tracking/QE processes.

@liggitt
Copy link
Contributor Author

liggitt commented Mar 14, 2016

limited changes to moving the description to the top and decreasing the header size

@liggitt
Copy link
Contributor Author

liggitt commented Mar 14, 2016

[merge]

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/5309/) (Image: devenv-rhel7_3718)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 64510a4

openshift-bot pushed a commit that referenced this pull request Mar 14, 2016
@openshift-bot openshift-bot merged commit 3941102 into openshift:master Mar 14, 2016
@mfojtik
Copy link
Contributor

mfojtik commented Mar 14, 2016

@bparees @deads2k i saw couple issues opened using this template and I don't think it makes the issue reading more complex... in fact it provides some clues for users where and how to get useful informations... for dev-dev I agree it is pain (ctrl-a+del ;-)

@liggitt liggitt deleted the issue-template branch March 16, 2016 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants