Hi ,
i want to sum story points with automation in jira, and made this logic.
i checked it, there is no "story point estimate" field for user story and task backend, but there is for web frontend. but it's ok for subtaks. which field i should use?
how can i fix it ? many thanks
for better understanding and further investigation: could you please explain what you are trying to solve with your automation rule from a use case perspective? What is your setting? when should the rule be triggered? which issues do you have in place? which story points from where would you like to sum and whaat for? what should they be used for?
Could you also share a screenshot of your current automation rule?
Best
Stefan
Hi @Stefan Salzl ,
what I want to do is to sum the story points of all subtasks automatically for one user story or task. and I created a new automation rule for it. and I activated the "story points" for estimation in the project setting=>feature.
I will attach the screenshot I have made in the automation rule.
The issue comes in the 3rd step "Edit issue fields", I can't find the "Story point estimate" in the dropdown list. and so, the rule can't run well.
looking forward to your solutions!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is your project team-managed or company-managed?
Could you please also share a screenshot of the configuration of your "edit issue fields" action?
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Guess I´ve got the problem already:
There is a different field for the estimation in team-managed and company-managed projects.
Within team-managed projects this field is called "Story point estimation". Unfortunately (as you already pointed out correctly) this cannot be chosen in the dropdown field so the advanced edit function via JSON needs to be used. I tried this in my environment and it worked (see the screenshot):
I´ll add this here as text so you can copy this directly:
{
"fields": {
"Story point estimate": {{issue.subtasks.Story point estimate.sum}}
}
}
Please give it a shot and let me know if it works.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am not sure whether is project team-managed or company-managed. the admin create a project for me in the corporation environment. which one it should be? or where can check it?
you can see the "Story point estimate" is prodived by jira, can't be modified.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the information and the screenshot. As the screenshot looks like it´s a team-managed project. I already assumed this. Please find the description and solution in my last answer above ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Further question:
Which issue type is the issue "PORTAL-485" that should be edited in your audit log screenshot?
From your former screenshot of issue types settings I can see that there is a field "Story point estimate" in issue type "Story".
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Stefan Salzl thx for your support.
I have no idea why it doesn't work for me. I need your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok. Thanks for your input. The edit issue fields action looks different now to your initial post as it now only shows "advanced" option (formerly: Story Points).
Let´s do a live example for investigation. If possible please try to reproduce as follows:
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a similar problem, following your steps. After I tried your suggestion before, it still shows like this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I could not reproduce this. If it still doesn´t work on your side could you also try to use the option via "customfield_id" instead of the fields name? On my side this looks like the following:
In case neither of these options works I would recommend to raise a support ticket with atlassian support.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Stefan Salzl
somehow I can't find the customfield_id because it seems like not a custom field.
Do I need to be an admin to raise a ticket?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.