Automation help

[Sushant Verma]

Automation

[John Funk]

Hi Sushant,

Basically, you want to create an automation with a Field Value Changed trigger for the dev effort field.

Take a look at this document and follow for Case # 2. 

Then you would do another rule for the qa effort following the same pattern.

Then you would do two more for story level being updated to update the Epic (parent). 

Be sure on each rule to check the box in the rule details for the Allow Rule Trigger function.

https://community.atlassian.com/t5/Jira-Software-discussions/3-Jira-automation-rules-we-will-cover-in-our-advanced-webinar/m-p/1398109#M2801%3

[Sushant Verma]

Thank you @John M Funk 

[Dave Mathijs]

Hi @Sushant Verma ,

Are you using those fields for Original Estimate?

I've had a client who created several custom fields for original estimate of business analysis, functional analysis, breakdown, project management, development, testing, etc.

They also used a third-party app to sum up those values into an original estimate.

Personally, I would recommend sumUp for Jira by Decadis.

On the other hand, why not create separate issues/sub-tasks for DEV and QA, each with their own original estimate (+ time spent and remaining estimage), rolled up to the Epic?

[Sushant Verma]

Hi @Dave Mathijs 

Thanks for your reply!

Yes, we are using this fields for original estimate. Could you please help me with that?

[Dave Mathijs]

It's a question asked before, have a look at the following question:

Sum numeric values from a custom field