Jira Automation

[Amit Agrawal]

Dear Team,

I have created a rule for my Employee System project. But it always shows the 'CONFIG CHANGE' status. Tried all the options but the rule does not apply. Request to please check and advise.

[Bill Sheboy]

Hi @Amit Agrawal -- Welcome to the Atlassian Community!

What is the type of your project: company-managed or team-managed?  You may find this information at the lower-left side of the page expanding area.

Company-managed projects use the "Story points" field and team-managed projects use the "Story point estimate" field...even though both are called "Story Points in the UX.

You rule is triggered on changes "Story point estimate", and so if your project is Company-managed the rule will not start.  Try changing to the other field.

Kind regards,
Bill

[Amit Agrawal]

My project is 'Team Managed Project' and not sure what is missing. Request to please check and validate.

[Bill Sheboy]

Thanks for that information.

Please post an image of a specific issue, showing the history where you have changed the Story point estimate value after your rule was enabled, on 10/12/23 9:28:54 pm.  And then post and image of the audit log details if there were any changes after that point in time.

Next, can you confirm what is the estimation measure for your team-managed project: story points or time?  You may find this information here:

left-expand area > Project Settings > Features > Estimation

[Amit Agrawal]

Attached are the required information.

[Bill Sheboy]

Please also show the history for a specific issue (e.g., a story) where the story point estimate changed after the rule was enabled. 

Also, you are using Time estimation, and not Story point estimation.  How will that work for your team as the field will not be shown on the view, by default?

[Amit Agrawal]

Yes, we are using estimation not story point because relation of story point with estimation is still to be validated. Very much comfortable for estimation on time.

It would be great if can connect on call to show you the live demo. Please advise.

[Bill Sheboy]

If you scroll down in the issue view for ES-131, you will find the Activity section, with a History tab.

Please select that, and find where the Story Point field was set after the rule was enabled.

If you are not setting the Story Point field, a rule triggered on changes to that field will never run, and that may explain what you are observing.

[Amit Agrawal]

Attached is the screenshot of the log. Rule was created before the task was created. My observation is that Rule doesnt work on the estimation and only works for user points field. Please advise. 

It would be great if we can connect to show you the issue live on my screen to get more clarity to reach the solution.

Thanks

[Bill Sheboy]

That shows the rule could never trigger: you are not using the story point field. 

If you want to sum the original estimate the rule must trigger on a change to that field.

[Amit Agrawal]

Not sure about your statement but I tried to edit the field after rule creation only. I create new task as well but none of the option working.

[Bill Sheboy]

I am unclear how else to explain this:

The rule you have shown is triggered on a change to the Story point estimate field, but you are not using that field.  Instead you are using time tracking for estimation.  And so your rule should be triggered on a change the estimate field that you want to use.

[Amit Agrawal]

Not sure about your comments. But I tried to sum up of original estimate of all sub-tasks in the Parent Task field (Create a custom field to store values). Trigger is on every action. Hope this clears what I am trying to achieve.

There are issues what I can see is that field in the sub-task is not available on the triggers. Another can be that custom field name is not recognized.

Hope the above clears your queries.

[Manoj Gangwar]

Hi @Amit Agrawal , 

Welcome to the atlassian community! 

Could you please share the automation rule screen so that we can check further? 

[Amit Agrawal]

Attached are the images for your reference.