-
Bug
-
Resolution: Fixed
-
Low
-
10.97.2
-
2
-
Severity 3 - Minor
-
No
Issue Summary
When Default User in Jira Settings (Administration → Connectors → Jira Settings → Jira Setup, Custom Fields → Default User) is not set to an existing user ID, Canceling a Synced Feature in Jira hides it in Jira Align instead of putting it in Canceled Bin
Steps to Reproduce
- Default User in Jira Settings is not set to an existing user ID
- The default is SaaSAdmin, set it to a wrong ID or non-ID (for example name)
- Have a Feature mapped to Jira Epic
- Have Canceled state mapped
- Move the Jira Epic to Canceled state on Jira side
- Check Canceled Items for Features
- Selecting the same program or all programs or any other options doesn't find it
Expected Results
In Jira Align the Feature should show in Canceled bin, per documentation, and also based on Stories behaviour in same scenario
Actual Results
The Feature cannot be found in Canceled bin, Recycle bin, Deleted items report.
When the Jira Epic is moved back out of canceled state on Jira side, the Feature is reinstated in Jira Align and Audit log continues correctly.
So it continues to be the same Database item.
Workaround
Set the Default User to an existing ID, then reinstate the Feature on Jira Software side and cancel it again.
- is cloned from
-
JIRAALIGN-3457 Canceling a Synced Feature in Jira hides it in Jira Align instead of putting it in Canceled Bin
- Closed
- mentioned in
-
Page Loading...
- resolves
-
ALIGNSP-10169 Loading...
-
ALIGNSP-11322 Loading...