Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
6.3.15
-
6.03
-
2
-
Severity 3 - Minor
-
1
-
-
Description
tl;dr Cloning issue ignores Requirements for having Versions field populated
Problem
Project requires that the "Affects Version/s" field be populated on new issue creation. If you clone an existing issue ticket that contains archived versions, the newly cloned ticket will not contain archived versions, this is the result of JRA-9005. The problem is that the current behaviour also results in the new cloned ticket have no defined "Affects Version/s", even if it is required. There is no warning or indication that "Affects Version/s" needs to be populated
Expected Behaviour
As "Affect/s Version" is a required field, it's expected that the user has to input a new version for the cloned issue ticket.
Steps to Reproduce:
- Create a project with a version
- Ensure that the the "Affects Version/s" field is marked as "Required" in the field config scheme
- Create a new issue ticket, populating the "Affects Version/s" field
- Archive the versions in the project
- Clone the issue ticket
- Notice that the newly cloned ticket's "Affects Version/s" field is blank
- There were no prompts, errors, or any indication that "Affects Version/s" field needs to be populated.
Attachments
Issue Links
- relates to
-
JRASERVER-9005 Cloning an issue copies fix versions for archived versions
- Closed