Hi there,
My ultimate goal is to sum up story points from all subtasks, with Story parent. I am aware about the existing automation rule, however before actually start using it, I have a few questions:
1. In my Jira instance on subtask screen, I can bring only Story point estimate field rather than Story Points - is there a way I can bring Story Points field to the Issue Screen? The funny thing is - I can see both field added into Issue Screen configuration, however only Story point estimate field is visible after all.
2. If after all I should go with Story point estimate rather than Story Points, then in Automation rule condition for Parent story point value, should I add {{issue.subtasks.Story point estimate.sum}} rather than {{issue.subtasks.Story Points.sum}}
3. Apart from the above change, do I need to change anything else in the Automation rule - I assume the condition also should change to Story point estimate, right?
I have a couple of questions that may help the community to offer you suggestions:
Best regards,
Bill
Thanks for initiating the discussion @Bill Sheboy please find my answers below:
I am working with the company, where we are applying Agile SCRUM framework in a kind of evolutionary way, but we are aiming what's described in Agile Project Management. For the moment we think we realize how to map the main logical domains there:
So this is pretty much the idea behind this request. I hope now it makes more sense to all of you. Let me know your thoughts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your detailed explaination!
Regarding the field issue, have you tried the field admin helper, as it would appear a field is not present in a setting/context/view. Please look here for how to use the helper as you are a site admin: https://support.atlassian.com/jira-cloud-administration/docs/use-the-jira-admin-helper/
Regarding the sizing of sub-tasks, I understand your meaning and I further wonder:
One way teams address this issue is during refinement, the team asks questions to confirm a shared understanding of the request's "why" and "what", discusses the solution approach as a team, and then sizes together as a team. They may then compare to prior work to achieve sizing alignment with better accuracy. Tools like a "sizing ruler", triangulation, or "things that matter sizing" can help.
Thanks again for your ideas!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Bill Sheboy - re Story - subtasks relation and SP calculation, you have a point, we will definitely address the issue. I think the key point here it to make sure, the approach, when we have a Story, which we can then broke it to subtasks is the best approach.
I tried to summarize all foreseen approaches I have in this discussion topic, I would appreciate if you or anyone else decides to provide their feedback.
Thanks agains!
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.