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?

[Nic Brough -Adaptavist- · Accepted solution]

Yes, it's perfectly safe and has only one minor downside - if you need to take the database offline for maintenance, all the applications suffer downtime.

[Sandeep Nagaraja]

Thanks Nic

Will there be any implications on performance.?

Also will we have issues upgrading the different apps at different times in the future ?

Are there any other advantages for keeping the databases separate (except for independence..so if db is down the app is not down) ?

[Nic Brough -Adaptavist-]

Performance - not really. Obviously, any database service can become overloaded, but there's nothing unusal about running several Atlassian apps in databases scattered across services or in one place.

Upgrading - not an issue - the sets of data are separate, so the upgrades are independent.

Other advantages - that's where I have to back away and defer to a real DBA. In terms of Atlassian stuff, there's nothing really other than the independence, but that applies to any application backed with a database.