-
Bug
-
Resolution: Fixed
-
Low
-
8.0.5, 8.1.0, 9.0.3, 9.1.1
-
None
-
Severity 3 - Minor
Issue Summary
This is reproducible on Data Center: (yes)
When we export an automation rule and subsequently import it on the same instance with a duplicate name, as per the functionality application should rename the automation rule with "Copy of " in the prefix. However, it fails to do so.
Steps to Reproduce
- Export the Automation Rule
- Now, import the rule to the same instance with the same name.
- While Importing the rule we get the below message "Please note that if a rule with the same name already exists, then the imported rule will be renamed to 'Copy of ...'."
- The imported rule is not renamed, and it retains its original name.
- However, the second time you import the same rule, it renames it with a copy of.
Note: This scenario occurs when the rule is exported and imported on the same jira instance. This issue is replicated on Jira versions 8.20, 8.22.6, 9.3.3, 9.4.0, 9.4.18, 9.5.0 and 9.12.5
Expected Results
Imported rule with the duplicate name should be renamed to "Copy of".
Actual Results
When the duplicate rule name is imported, the name remains unchanged.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
[JIRAAUTOSERVER-1009] Importing the automation rule with a duplicate name does not rename it by adding the value "Copy of" in the prefix.
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 10.0.0 [ 108103 ] | |
| Fix Version/s | New: 9.2.0 [ 108102 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Assignee | New: Anna Przybycień [ 5b2ccddb8927 ] |
| Status | Original: Gathering Impact [ 12072 ] | New: In Progress [ 3 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Description |
Original:
h3. Issue Summary
This is reproducible on Data Center: (yes) When we export an automation rule and subsequently import it on the same instance with a duplicate name, as per the functionality application should rename the automation rule with "Copy of " in the prefix. However, it fails to do so. h3. Steps to Reproduce # Export the Automation Rule # Now, import the rule to the same instance with the same name. # While Importing the rule we get the below message *"Please note that if a rule with the same name already exists, then the imported rule will be renamed to 'Copy of ...'."* *!Screenshot 2024-04-02 at 1.02.12 PM.png|width=427,height=181!* # But the imported rule is not renamed and is imported with the same name. !Screenshot 2024-04-02 at 2.51.42 PM.png|width=481,height=157! # However, the second time you import the same rule, it renames it with a copy of. !Screenshot 2024-04-02 at 2.32.36 PM.png|width=480,height=157! *Note:* This scenario occurs when the rule is exported and imported on the same jira instance. This issue is replicated on Jira versions 8.20, 8.22.6, 9.3.3, 9.4.0, 9.4.18, 9.5.0 and 9.12.5 h3. Expected Results Imported Rules with the same name should be renamed to "Copy of". !Screenshot 2024-04-02 at 2.55.01 PM.png|width=511,height=167! h3. Actual Results The duplicate rule has the same name when it is imported. !Screenshot 2024-04-02 at 2.56.18 PM.png|width=478,height=156! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
This is reproducible on Data Center: (yes) When we export an automation rule and subsequently import it on the same instance with a duplicate name, as per the functionality application should rename the automation rule with "Copy of " in the prefix. However, it fails to do so. h3. Steps to Reproduce # Export the Automation Rule # Now, import the rule to the same instance with the same name. # While Importing the rule we get the below message *"Please note that if a rule with the same name already exists, then the imported rule will be renamed to 'Copy of ...'."* *!Screenshot 2024-04-02 at 1.02.12 PM.png|width=427,height=181!* # The imported rule is not renamed, and it retains its original name. !Screenshot 2024-04-02 at 2.51.42 PM.png|width=481,height=157! # However, the second time you import the same rule, it renames it with a copy of. !Screenshot 2024-04-02 at 2.32.36 PM.png|width=480,height=157! *Note:* This scenario occurs when the rule is exported and imported on the same jira instance. This issue is replicated on Jira versions 8.20, 8.22.6, 9.3.3, 9.4.0, 9.4.18, 9.5.0 and 9.12.5 h3. Expected Results Imported rule with the duplicate name should be renamed to "Copy of". !Screenshot 2024-04-02 at 2.55.01 PM.png|width=511,height=167! h3. Actual Results When the duplicate rule name is imported, the name remains unchanged. !Screenshot 2024-04-02 at 2.56.18 PM.png|width=478,height=156! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |