> From that point of view I'd wish that people stopped flagging the
> "fix for" unless there is something backing the work to fix the issue,
> otherwise people look at jira and say "oh, this one is scheduled for
> 2.1.4" when that one has been around since, maybe, 2.1-beta1,
> has just been moved forward over and over, and it's not
> really going to be fixed anytime soon (just making it up, don't know
> if there is any issue in the state I've described, but I've seen many
> being just moved forward repeatedly).
>
>
>
I have had a look at the administration options; and I think Jira could be
configured to hide that field until the last two stages of the workflow
(Resolved/Closed).
So the workflow would be something like:
0) Issue is created, gets patched, and is eventually ...
1) marked as resolved … fill in the "fix for" version at this time
2) Leave it open while waiting for confirmation from user list; and close the
issue if you get confirmation
3) In the real world - close the issues when the release goes out
I no longer have super-admin access on Jira; but I can see the admin options
that would let
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
