Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
I assume also the APIs related to epics will be changed as well. For example, we use the APIs
/rest/agile/1.0/board/{boardId}/epic?done=true and
/rest/agile/1.0/board/{boardId}/epic?done=false, I assume they will start returning the epics based on the Issue Status Category now (instead of Epic Status) and we can rely on that.
Looking forward to these changes from my side. One question I have: Is there a JQL query I could run to see if there are any Epic's where the Epic Name value is not the same as the issue summary?
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
That type of field-to-field comparison is not possible with the built-in JQL features; it is not a SQL.
If you have one of the marketplace addons for JQL, this type of comparison may be possible.
If not, I would suggest exporting your epics to a spreadsheet to perform the comparison.
There are some other suggestions in this thread for keeping these fields in synch using automation rules. Please look back in the thread to find those, if you wish.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
@Rohan Swami1 Do you know if this is still scheduled for March 22nd, 2023? I know I saw a post stating that but I am not able to find that post anymore. We may have some work to do before this rolls out and trying to prioritize my teams work.
When will you be introducing the ability to query for issues by parent (i.e. Epic), including querying based on the Status or Status Category of the parent?
@Jeno Fernando - I don't work for Jira but personally I would migrate to cloud before this change. There have been changes on cloud over the last couple of years that you may've not received on server. UI and behavior changes. I'd give your team time to work through the potential migration issues to cloud without the added Epic issues. Some of those changes took a bit of correction time in my environment. There wasn't a solid migration on some of the UI changes.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
I received an automated email from Atlassian 2nd Feb, within it they state "These changes are due to roll out on March 22nd, 2023." Not had anything since then, but have communicated out that date internally.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
I'm having some trouble with that changes as below:
I created an automation rule to create an Epic when an issue in Jira SM was transitioned to a specific status. However, to be updated with those recent changes, I tried to remove the Epic Name field from my automation, and the result wasn't like the expected and explained in this post. Actually, my automation is getting crashed after the field remotion.
What can I do right now? Rollback the updates made by myself?
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
228 comments