-
Bug
-
Resolution: Not a bug
-
High
-
None
-
Severity 2 - Major
-
Issue Summary
Within the Automation editor, sprint related actions, such as "Create Sprint" are suddenly missing as options. Documentation in https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-sprint indicates this is an option of any Jira Software Cloud site.
Tested against Company managed Scrum project, team managed project with board/sprints enabled, and global automation.
Steps to Reproduce
- Within a Jira Software project, go to project settings and Automation
- Create a new rule with any trigger, and then create a new action
- Search for an action called 'sprint' OR don't search and navigate to "Jira Software" specific actions
Expected Results
We expect actions
- Create Sprint
- Complete Sprint
- Start Sprint
to be selectable options here
Actual Results
All of these sprint related actions are missing
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
[JSDCLOUD-14150] Sprint related actions like "create sprint" are missing from the automation editor
Hey folks!
I handle the documentation and in-product content for Atlassian Automation. Just wanted to pop in and repost my comment from this Community post, to clear the air around what happened with these sprint actions.
Long story short, this content was published by mistake.
Some time ago, we were working on sprint-related actions for Jira Cloud Automation - Create sprint, Start sprint, and Complete sprint. We had designs for these actions ready to go, and our dev team had started building them. At this point, I drafted the content and got it ready for publishing.
As is often the case, priorities changed - we had to stop working on the sprint actions, to focus on other projects. Months later, I published the content for the sprint actions by mistake while publishing something else.
This error managed to slip under my radar and remained undetected until last week, when AUTO-892 was raised. At that point, having realized what happened, I immediately removed all mention of the sprint actions from the docs.
So, in summary:
- The sprint actions (Create sprint, Start sprint, and Complete sprint) never existed in the product.
- These actions did appear in our documentation, but this was by mistake.
- We don't have any components that are exclusive to the Enterprise plan.
I'm really sorry for all the confusion caused by my goof-up - this is completely my mistake. I hope this comment clears things up.
Greetings!
Why is there no statement to indicate why this was closed as "Not a bug"? For example, is there a change of direction to partition the triggers/actions/etc. for Jira Cloud automation by license level, similar to what was done for the free/pro versions for Jira Server / Data Center?
Until these previously offered actions are re-added for all license levels, a work-around is to call the relevant REST API functions from the rule. Although that work-around will be much more complex due to the need to correctly identify the relevant sprint to impact.
OH, maybe the fact that they were documented (but perhaps not yet implemented) was the actual "bug".
Not that we're keeping score, but this was first reported by @billsheboy over in the Community Forums: https://community.atlassian.com/t5/Automation-questions/automation-is-missing-sprint-related-actions/qaq-p/2476910
OK if this is not a bug and a mistake, I still want to be able to create a sprint through a simple automation action, can you please advise where there is a request I can vote for? And as you planned to do this previously, can we expect that they are still on your radar to be delivered?