-
Bug
-
Resolution: Timed out
-
Medium
-
Severity 2 - Major
-
0
Issue Summary
In an automation rule, using the action Transition Issue to copy status from a team-managed project issue to a company-managed issue project fails with a "Destination status could not be resolved" error.
Steps to Reproduce
- Create a rule to manually trigger from a team-managed project.
- Set the rule to copy to a destination issue is in a company-managed project (such as created by a clone action).
- Add the action Transition Issue with the destination status set to Copy from trigger issue
Expected Results
The destination issue has a matching status as the source trigger issue.
Actual Results
The rule fails with the following audit log error:
Transition issue Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
[AUTO-383] Transition Issue Action Fails to copy Trigger Issue Status from Team-Managed to Company-Managed Project
Resolution | New: Timed out [ 10 ] | |
Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
Labels | Original: jsw-s13 tmp | New: cll-tf3202505 jsw-s13 tmp |
UIS | Original: 3 | New: 0 |
Labels | Original: jsw-s13 | New: jsw-s13 tmp |
Labels | New: jsw-s13 |
Remote Link | New: This issue links to "Page (Confluence)" [ 759473 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 758790 ] |
Component/s | Original: Automation - Actions [ 69594 ] | |
Component/s | Original: Automation [ 68402 ] | |
Component/s | New: Trigger - Other [ 70304 ] | |
Component/s | New: Trigger - Other [ 70304 ] | |
Key |
Original:
|
New:
|
Support reference count | Original: 4 | |
Project | Original: Jira Software Cloud [ 18511 ] | New: Automation for Cloud [ 22610 ] |
Support reference count | Original: 3 | New: 4 |