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

Include version on feature-request template #478

Merged
merged 1 commit into from
Jun 24, 2020

Conversation

jotoeri
Copy link
Member

@jotoeri jotoeri commented Jun 20, 2020

For easier processing of requests, especially if we think they are done already.

@jotoeri jotoeri added the 3. to review Waiting for reviews label Jun 20, 2020
@jancborchardt
Copy link
Member

I'd say put the current server version in (19.0.?) and also the anticipated new Notes release (2.0.0), that way people see what they ideally should be using. :)

@jotoeri
Copy link
Member Author

jotoeri commented Jun 21, 2020

Thats good idea, yes 👍
Would you mind to have a look onto both templates again (feature-request & bug-report) from side of UX?
How do we get users to really use the templates and provide us the information, we need? It happens (quite often), that users don't use esp. the bug-template...

@jancborchardt
Copy link
Member

Would you mind to have a look onto both templates again (feature-request & bug-report) from side of UX?
How do we get users to really use the templates and provide us the information, we need? It happens (quite often), that users don't use esp. the bug-template...

The biggest issue usually is that the template is too long, but that’s not the case here. Might just be a matter of if anything is missing to ask people to use the template (and not individually asking "what’s the version" etc.).

@jotoeri jotoeri force-pushed the enh/feature_template_version branch 2 times, most recently from 6df4bb2 to d4d17e1 Compare June 22, 2020 09:57
@jotoeri
Copy link
Member Author

jotoeri commented Jun 22, 2020

Hm, ok... So then this one should be good to go now...?

@jotoeri
Copy link
Member Author

jotoeri commented Jun 22, 2020

Ah - or how do you think about shortening the first text as in the fixup? I think i personally would also wonder, if i first get told 'how to use the website'.

@jancborchardt
Copy link
Member

Ah - or how do you think about shortening the first text as in the fixup? I think i personally would also wonder, if i first get told 'how to use the website'.

Yeees! So much better, and it's not so confusing. I was also always wondering if that is something to remove, but it's there for peopel reading the issue. :D

Signed-off-by: Jonas Rittershofer <jotoeri@users.noreply.github.com>
@jotoeri jotoeri force-pushed the enh/feature_template_version branch from 7c93d23 to b899ed2 Compare June 22, 2020 10:48
@jancborchardt jancborchardt added the enhancement New feature or request label Jun 24, 2020
@jancborchardt jancborchardt merged commit c3a3541 into master Jun 24, 2020
@jancborchardt jancborchardt deleted the enh/feature_template_version branch June 24, 2020 14:04
@jancborchardt jancborchardt added this to the 2.0 milestone Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants