I'm trying to set up an automation to help with the following issue:
I've tried going at it with:
Have anyone made a similar automation with success? Or has any other ideas on what I might try?
First thing, I find putting story points at the sub-task level seems both different than the intent of using sub-tasks (i.e. non-releasable child items which contribute to building a releasable thing, such as a story) and to create busy work to gather the measures later for team use. With that out of the way...
Perhaps check if the Issue Moved trigger is fired when the subtask changes issue type, and if so, then use the changelog to find the parent story and modify it (e.g. a comment) to trigger a different rule to refresh the original parent's data.
Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events