|
History
| Log In
|
|
|
|
Hi,
I mean that an issue can have a released affects version, but a released fix version should not be selectable while issue creation. For me that makes no sense to add a new issue to a version which is already released/live. Hi Marcus,
The functionality is intentional. However, I definitely see what you mean. This functionality will be a lot easier to implement after JIRA 3.2 is released as a lot of 'issue field' related code has been refactored. Also please note that the fix version field can only be set by users with Resolve Issue permission. So you have some control over who is allowed to set and update the field. Thanks, Anton,
this control we cannot use, At the moment during every workflow phase everybody with "Resolve Issue permission" can add issues to old released version. we cannot really wait for 3.2 version, This would need to be an option, because in many cases (in JIRA development, for example), it is necessary to mark a bug fixed-for a released version (eg. when a bug is not properly identified until after the release cycle). When resolving an issue, the 'released' versions are clearly separated in the 'fix version' field. Could users not just be trained to not fix bugs in released versions?
This is not an option for us, we have a lot of non-technical or alternating JIRA-users (QA and issue/requirements planner) and theire modification attempts in JIRA should be control by JIRA itself.
User-Training is useful, but for this operation not possible. "Adding issues to released Versions" must be controlled by JIRA itself. (e.g. configurable for different situations, i understand your workflow in JIRA development, but in our company this behaviour isn't understandable. This "To be an option" is the needed choice for us. Possible? Yes, I mean that since both use-cases are valid, JIRA's behaviour would need to be specified via an option in the admin section.
Given the number of things happening at the moment, it is doubtful whether we can implement this soon. If it is urgent, I'd suggest trying to implement it yourself. The 'Fix versions' list is generated in create_versions.jsp, calling CreateIssueDetails.getPossibleVersions() (from a superclass). You would need to create a new getPossibleFixForVersions() method returning only unreleased versions, and then call it from create_versions.jsp – Hi,
I need exactly the same and I would really appreciate an option in the admin section to configure that adding issues to released versions is not possible. Please can you implement this in a near future version? Hi,
I confirm this improvement is not an option for us. The risk to miss an issue simply because it's assigned to the released version is too high. The solution looks simple. It shouldn't therefore be too complicated to add it in standard in a next fix, no ?  I can't convey how difficult this issue is for us. We have non-technical clients, fairly unfamiliar with Jira entering issues. Since they are essentially product managers, it is necessary for them to prioritize issues into versions. We have many, many clients and absolutely cannot try and educate them all to make sure they do not do this.
Further, we base many of our contracts, and the basis of project completion on Jira. If we think we have everything completed, only to look at the changelog and find more issues, this can wreak havoc on our scheduling/planning overall. THIS IS A BIG DEAL. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Adding Issues to released Versions
This is done on purpose. Bugs can still be found against the "live" version? Is this what you mean?
Cheers
Mark C