In Automation can a Parent be hardcoded in that field?

[Mark Williams]

Has anyone ever seen in automation a hardcoded Parent to have fields updated on the creation of another ticket?

[Bill Sheboy · Accepted solution]

Hi @Mark Williams 

Do you mean something like this:

GIVEN there is an existing issue-X
WHEN a new issue is created that could be a child of issue-X
THEN the new issue's parent is set to issue-X
AND specific fields from issue-X are copied to the new issue

If so, yes, that is possible.  Try hardcoding the parent issue's key in JQL within the rule, such as with the Lookup Issues action, and then reference the result to set fields in the newly created issue.

Kind regards,
Bill

[Kalyan Sattaluri · Accepted solution]

Hello @Mark Williams 

Can you expand further on your requirement or use case?

Are you creating an issue with hard coded Parent and you want to update some fields of the Parent issue after you have created the other issue? Is that the requirement?

[Mark Williams]

If an issue type equals xxx

Then: Edit issue fields where Parent is hardcoded Ticket-1234 instead of using Trigger issue/current issue.

Components are updated

 Labels 

Sprint

Story Points 

Assignee

for TICKET-1234

[Kalyan Sattaluri]

Apologies but I am confused by your use of "hardcoded ticket=1234".. Do you mean to say the trigger issue has a parent which is they 1234?

Typically, when you have to update related issues such as Parent or child, you use branch, so that rule will look like:

• Trigger = Issue created (or field changed)
• If condition = Issue Fields Check = Issue type = XXX
• Branch = on Parent
  • Edit Issue = Update Labels, Sprint, Story Points, Assignee

But need more info on what is your trigger, what type of issue will pass your trigger in If condition (sub task?), cause these details drive what you choose in branch. 

Please share more details on above, maybe try implementing the rule share screenshot... hope it helps. Thanks!

[Mark Williams]

Yes, in the Parent field in stead of using Trigger Issue or Current Issue... The user has hardcoded Ticket-1234 to update.  So every time this automation rule runs it will update Ticket-1234.  I thought this was odd and just wanted clarification. 

You can consider this issue resolved.