Skip to content

Require a problem description in issues #14032

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

Closed
wants to merge 1 commit into from

Conversation

jankatins
Copy link
Contributor

Currently some issues are just code examples without a description why a change should be done. This leads to problems when (years later) the current behaviour is questioned and no one can remember why it was changed.

Currently some issues are just code examples without a description **why** a change should be done. This leads to problems when (years later) the current behaviour is questioned and no one can remember why it was changed.
@sinhrks
Copy link
Member

sinhrks commented Aug 18, 2016

I think it may better to be added:

  • checkbox whether the reporter uses the latest version
    • reason otherwise

needs discussion though

@jankatins
Copy link
Contributor Author

jankatins commented Aug 18, 2016

In Addition to the reason why the thing is actually a problem?

@jreback
Copy link
Contributor

jreback commented Aug 18, 2016

@jankatins
Copy link
Contributor Author

See also #14031 for basically the same thing for PRs. That one also has a small example why I think such a description is needed.

@TomAugspurger
Copy link
Contributor

TomAugspurger commented Aug 18, 2016

The addition seems fine to me.

@@ -1,3 +1,7 @@
#### Problem description

[this should explain **why** the current behaviour is a problem and why the expected output is a better solution.]
Copy link
Contributor

Choose a reason for hiding this comment

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

what do the [ ] do here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My idea was to indicate that this text should be replaced.

@jreback jreback added this to the 0.19.2 milestone Nov 18, 2016
@jreback jreback closed this in f26b049 Nov 18, 2016
@jreback
Copy link
Contributor

jreback commented Nov 18, 2016

ok, let's see how this works.

thanks @JanSchulz

@jorisvandenbossche jorisvandenbossche modified the milestones: 0.20.0, 0.19.2 Dec 14, 2016
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