-
Bug
-
Resolution: Fixed
-
Low
-
6.3.8, 6.4
-
6.03
-
Actually this issue is a composition of few other behaviours, which combined allows to do this.
1. IssueInputParameters with applyDefaultValuesWhenParameterNotProvided flag set also provides default resolution and resolution date in generated issue input
2. While creating issue the resolution is discarded but resolution date is not. This caused SW-892
public void store() { try { if (!isCreated()) { //(...) fields.put(IssueFieldConstants.RESOLUTION_DATE, resolutionDate); //(...) } else { // Otherwise, just update the record of the issue genericValue.store(); } } catch (GenericEntityException e) { throw new DataAccessException("Error occurred while storing issue.", e); } }
3. During issue creation the issue is indexed few times, where the first one still contains resolution set by (1) which sets index for very limited time in invalid state. This probably caused SW-673
The first reindex:
The second reindex:
- causes
-
JSWSERVER-11409 Issues created via 'Quick create' method in planning mode of Jira Agile - show up in Activity stream as 'done'.
- Closed
-
SW-673 Loading...
-
SW-892 Loading...
- is duplicated by
-
JRASERVER-42827 IssueService IssueInputParameters setApplyDefaultValuesWhenParameterNotProvided
- Closed
- is related to
-
JPOSERVER-2016 Default Resolution causes issues to be committed with Resolution Date
- Closed
-
JSWCLOUD-19196 Default Resolution causes issues to be committed with Resolution Date
- Closed
- included in
-
CPU-209 JIRA 7.1.0-OD-04-012