[#JRA-7196] Releasing a version and moving open issues to the next version is not logged in affected issues' change history

JIRA

Releasing a version and moving open issues to the next version is not logged in affected issues' change history

Created: 30/Jun/05 08:03 AM Updated: 30/Jul/06 07:35 PM

Component/s:

None

Affects Version/s:

3.0.1, 3.2.1

Fix Version/s:

3.3 Beta1

Time Tracking:

Not Specified

Participants:	Anton Mazkovoi [Atlassian], Dylan Etkin [Atlassian] and Frank Schimmel
Since last comment:	3 years, 21 weeks, 4 days ago
Resolution Date:	07/Jul/05 12:29 AM
Labels:

Description

« Hide

USE CASE:
Release a version with some still open issues.
Select to move open issues to the next version.

PROBLEM:
In the affected issues' change histories, this change in "Fix Version/s" is not logged.

NOTE:
When using bulk edit to change the "Fix Version/s", the change history of the edited files is updated correctly.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Frank Schimmel added a comment - 30/Jun/05 09:05 AM

Also there is no e-mail triggered by such an event.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 30/Jun/05 11:39 PM

Thanks for reporting.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 30/Jun/05 11:40 PM

As you have mentioned, the workaround is to bulk-edit the issues before releasing the version.

Anton

[ Permlink | « Hide ]

Dylan Etkin [Atlassian] added a comment - 07/Jul/05 12:29 AM

Changed the moveUnresolvedToNewVersion method to use the IssueUpdate action to modify the issues instead of directly changing the association as it used to. This is so that change history will be generated and the edit event will be fired.