We have hierarchy as portfolio epic > epics> tasks>subtasks.
I need help on, when an portfolio epic is assigned to team ( We have a field named Team) automatically automatically all the issues(epics, stories .....) under that portfolio epic should be assigned to that same team.
Please let me know if there is a way.
I don't think @Vikrant Yadav solution is what you are after @Nagarjuna Busireddypally as you want to populate the hieratical children, not the linked issues.
I would go about like this.
Trigger: Field (Team) has been edited
Condition: and Team is not empty
Branch: by JQL
issue in portfolioChildIssuesOf("{{triggerIssue.key}}")
Action (on the branch): Edit issue. And populate the team using as below.
Thanks @Curt Holley I think this is the correct approach.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Curt Holley
Thank you for suggestion.
Can you please also help me on this.
When story points for epic is updated, it should automatically update the story points in parent (Portfolio epic), for eg if the aa-1,aa-2 is the epics, aa-3 is the portfolio epic, if we update the story points for epics aa-1, aa-2 it should automatically update story in portfolio epic aa-3
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It will go much like this Solved: How do you sum up story points to the epic using j... (atlassian.com)
But taking it up a level so that the 1st condition is Type = Epic
and the branch will need to point at the Portfolio Epic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Curt Holley
Yeah i tried this way,
1) Value changes for story points
2) Issue type equals epic
3)then look up issues "parent link" = {{triggerIssue.parent link}}
4) For parent branch
5) re fetch issue data
6) edit issue fields story points {{lookupIssues.Story Points.sum}}
Please let me know where i have done the mistake
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As mark point out here When story point in epic is updated, it should upd... (atlassian.com) your branch needs to be getting the Parent Link from the issue (in this case, the Epic)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
BTW @Nagarjuna Busireddypally could you accept my initial answer, so as to help confirm that it solved the issue and help inform others in the community. Cheers!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Curt Holley
I have accepted the answer, could you please detail the automation steps of the one i have asked.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
if you make your branch this, the rest should work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nagarjuna Busireddypally You can do this easily using Project Automation.
Select "Edit Issue" trigger >> Add condition >> Branch For Linked Issue >> Select "All Link Type" >> Edit Issue action >> Update Team field.
Similar post :- https://community.atlassian.com/t5/Jira-questions/Update-Linked-issues-by-automation-rule/qaq-p/1996757
Thanks,
V.Y
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.