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 as it is out and tests his issue with this new release. In case the fix did not really fix the issue in question, the reporter changes the jira issue to "reopened" and sets the fix version field to "unknown". This is the idea behind this permission, I think.
--Manfred On Feb 6, 2008 12:31 PM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > 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 very frequently: at least it is useful to > > schedule on a branch or on the trunk. > > yeah, I was unclear. > let's say it this way: > -an issue-filer (a non-committer) should not be able to edit this field. > > -M > > > > > Antonio > > > > > > > > -- > > Matthias Wessendorf > > further stuff: > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > mail: matzew-at-apache-dot-org > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
