nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Automation Story Point Estimate

Yash Attal

For Next-Gen JIRA Automation, I am trying to sum the story point estimate of the subtasks into the story point estimate field of the story. Unfortunately, under the edit issue action, I cannot find the field story point estimate at all. How do I get the story point estimate field to appear for the story so that I can set up the smart value?

Accepted answers

All comments

Petter Gonçalves

Hello @Yash Attal

Thank you for reaching out.

Indeed, Next-gen specific features and custom fields (as Story Point Estimate) are not properly rendered by Automation for Jira. The reason behind this behavior is that Next-gen uses different APIs for these features, so they are not properly recognized/mapped in Jira automation.

That being said, we have a feature request opened to adjust the Next-gen API with Jira Automation:

- NextGen Software projects are fairly broken in cloud

Please, keep an eye in that feature request to receive any updates about its fix implementation. Since the automation for Jira app was recently acquired by Atlassian, we also have now our own development team engaged to improve the integration with next-gen projects. Hopefully, we will have good news to share about this anytime soon.

Let us know if you have any questions.

Willie Husselmann

Any further updates on this?

Victoria Santos_6ddw25

So... let me understand this correctly. Atlassian released a "fairly broken" product and teams that received emails to update to "Nextgen" projects are basically crap out of luck?
Automated reporting is basically useless unless you manually update the story level points. What is the ETA that Atlassian will make "Nextgen" projects a "fairly" working product?

Petter Gonçalves

Hello @Victoria Santos

Sorry that we gave you this perception and feeling about the Next-gen projects. Please, allow me to clarify some concepts so we can confirm we are on the same page here:

Jira automation is not a functionality developed by Atlassian. In fact, it was developed by a third-party partner (Codebarrel) and acquired by Atlassian a few months ago. Before that, it was a third-party app that had a separate billing.

Jira Automation was developed to work with Classic projects, years before even the creation of Next-gen projects. Since Next-gen projects were created to use unique entities and a completely different architecture as a simpler solution, Jira automation does not work properly for Next-gen projects and it was defined that updates must be done.

With the acquirement and integration of the automation app to the main Jira application, we started to work to get those bugs fixed, while some of them have proved to be really difficult to address due to the different architecture of both Project types.

That being said, Next-gen projects are not a "fairly broken" project type, however, it does not work properly with the recently acquired automation functionality due to the initial architecture used for both applications which were related to two completely different DEV teams (Atlassian and Codebarrel).