You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2013/06/20 22:56:21 UTC
[jira] [Created] (INFRA-6424) Cassandra JIRA - rename 'Affects
Version/s' and add 'Reproduced In Versions' field
Aleksey Yeschenko created INFRA-6424:
----------------------------------------
Summary: Cassandra JIRA - rename 'Affects Version/s' and add 'Reproduced In Versions' field
Key: INFRA-6424
URL: https://issues.apache.org/jira/browse/INFRA-6424
Project: Infrastructure
Issue Type: Improvement
Security Level: public (Regular issues)
Components: JIRA
Reporter: Aleksey Yeschenko
Priority: Minor
We'd like to:
1. rename 'Affects Version/s' field to 'Since Version' (and make it a single-value field)
2. add new 'Reproduced In Versions' field (multiple-values)
Currently we have the default Jira field "Affects Version/s." It is
not reasonable to add 20+ versions for long-standing issues, so by
convention we set this to the earliest affected version, and assume it
is present in future versions until Fix Version.
However, users tend to set this to whatever version they are running
when the ran into a problem.
This is why we want to rename 'Affects Versions' to 'Since Version', and
make it a single-valued field. Then add a 'Reproduced In Versions'
field that people can set to their test environments.
Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira