Comments
-
Just tested this: Jira stories with 0.5 points or fewer will appear in Jira Align with 0 LOE. Jira stories with greater than .5 points will appear in Jira Align with 1 LOE.
-
Bulk Edit to remove a closed sprint from an issue works on Jira Server but there is an open bug on Jira Cloud: https://jira.atlassian.com/browse/JSWCLOUD-17215 The alternate solution for Jira Cloud is to reopen the sprint, move the issue to the backlog, and then reclose the sprint. That approach is described…
-
Article has been updated with the correct steps to take when this situation occurs. If it's not possible to get users to update their Atlassian profile, then Tim's suggestion to create minimal accounts is a great one.
-
Thanks for the clarification, @Rae Gibbs and @Tim Keyes !
-
One way you can run into this problem is if you are trying to update a Jira Align work item that is connected to a Jira issue that has been Resolved. You will need to "Unresolve" the issue in Jira before you can update states or process steps in Jira Align successfully. Check out this article for how to configure your Jira…
-
Also make sure that your Admin>Program>Manage>Dependencies>Manage External Entities toggle is turned on. I did that but still didn't see the More Actions button until I read your article. Thanks, @Mark Cruth !
-
You can follow these steps to re-authenticate if you have previously created the Jira Application Link while a Jira Admin and people are wondering why you are creating so many issues in their project. When you are done, it makes sense to validate that Issues are syncing from and to Jira Align. If you don't see issues…
-
A Jira Align Super Admin can initiate the OAuth authentication but the person who allows the OAuth handshake on the Jira side via Application Links should be logged into Jira as a Service Account. For a related great article on the steps involved when using Cloud Jira, check out:…
