our jira instance has these fields (and more...):
Fix Version/s:
Affects Version/s:
Both are editable by the bug filer.
The Affects Version/s: makes sense, since they need to identify the
broken version.
Now, I have problems in understanding the Fix Version/s field.
I understand it this
On Feb 6, 2008 12:01 PM, Manfred Geiler [EMAIL PROTECTED] wrote:
Matze,
This is a (hardcoded?) Jira feature.
I don't know.
There is one special issue permission in Jira that controls who is
allowed to assign a fix version:
Resolve Issues (Ability to resolve and reopen issues. This includes
Matze,
This is a (hardcoded?) Jira feature.
There is one special issue permission in Jira that controls who is
allowed to assign a fix version:
Resolve Issues (Ability to resolve and reopen issues. This includes
the ability to set a fix version.)
Since it is necessary for the reporter to be able
Yes, and this is only possible by taking away the Resolve Issues
permission for reporters (=issue-filers) which would also forbid the
reporter to reopen an issue.
Question is: do we want this.
My feeling is: no, because: In a perfect world :-) the reporter
downloads the fix version release as soon
2008/2/6, Matthias Wessendorf [EMAIL PROTECTED]:
but the Fix version/s should
be only for the committer, when closing.
Not only when closing. It can be used to schedule tickets. At Struts and
Tiles we use this technique very frequently: at least it is useful to
schedule on a branch or on the
On Feb 6, 2008 12:29 PM, Antonio Petrelli [EMAIL PROTECTED] wrote:
2008/2/6, Matthias Wessendorf [EMAIL PROTECTED]:
but the Fix version/s should
be only for the committer, when closing.
Not only when closing. It can be used to schedule tickets. At Struts and
Tiles we use this technique
On Feb 6, 2008 12:44 PM, Manfred Geiler [EMAIL PROTECTED] wrote:
Yes, and this is only possible by taking away the Resolve Issues
permission for reporters (=issue-filers) which would also forbid the
reporter to reopen an issue.
ah...
Question is: do we want this.
no :)
My feeling is: no,
