Unable to add parent key to a task.

[Mariam Abraham]

Hi, I'm currently working on automatically adding a parent key to a task on a "company-managed business" type project. I tried the same for "team-managed software" project and it was successful. It would be really helpful if someone could help me understand the reason me facing this issue is because of the different type of project configurations or due to some other reason.

[John Funk · Accepted solution]

Hi Mariam - Welcome to the Atlassian Community!

Team-managed projects use the parent key for Epics. But Company-managed projects use the Epic Link field. 

[Mariam Abraham]

Thank you so much!

[John Funk]

You are very welcome!

[Bill Sheboy]

Hi @Mariam Abraham -- Welcome to the Atlassian Community!

Yes, and...to what John suggests:

The "epic link" field is being deprecated for the REST API, and so will be removed for automation rules also.  The timeline for this appears to be around May 2022, so I recommend watching this post for information updates: https://community.atlassian.com/t5/Jira-articles/REST-APIs-and-webhooks-deprecation-of-the-Epic-Link-Parent-Link/ba-p/1873986

Atlassian notes they will try to automatically update rules, but edge cases may not switch over.  Those would require rule writers to update them manually to use the Parent field.

Kind regards,
Bill

[Mariam Abraham]

Hi @Bill Sheboy , Thanks for the information. 

I came across another issue while working on "team-managed software" project, i was unable to update the "issuetype"  to subtask automatically.

Does the project restrict from adding a task as a subtask automatically?

[Nic Brough -Adaptavist-]

No, you can convert issues to sub-tasks, but you do need to specify a parent issue when you do it (which is not the "parent link", it's the sub-task parent)

[Mariam Abraham]

Thank you!