Introducing the new Parent field in company-managed projects

[Konstantin Kulishenkov]

Hi @Steffen Edinger, would you be able to create a support ticket with this problem so we could investigate that in the affected Jira instance?

I've tried reproducing this, having switched my user language to German. The Parent (Übergeordnet) dropdown worked correctly for me - it was not empty. I tested that on Issue View, Issue Create, Transition Screen, and Bulk Edit.

Issue View:

 

Transition Screen / Bulk Edit:

Thanks,
Konstantin

[Konstantin Kulishenkov]

Hi @Antoine [Klee Group], thanks for reporting this issue with Transition Screens not having the Parent field added automatically (where there was Parent Link or Epic Link).

The fix has been implemented and is currently being rolled out, ETA next week. Until then, the workaround is to add Parent to these screens manually.

Thanks,
Konstantin

[Konstantin Kulishenkov]

Hi @Mélanie Liguet, please refer to this announcement for the REST API changes: https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048

Yes, your company should modify the bots to only use the new functionality from the announcement above. The old fields are still working, but they are past their deprecation notice (Nov 2022), so they may be removed at some point.

When we have the date of when Epic Link and Parent Link will be removed from Jira and REST API, we will announce that separately (cc @Luís Guedes da Silva). At this stage, we don't have a date to share.

Thanks,
Konstantin  

[Konstantin Kulishenkov]

Hi @Paddy Walsh, thanks for reporting this issue.

Jira has internal validation for the "Parent" hierarchy level. It will not allow to create invalid hierarchies, so there's no need for any custom validation to achieve that.

Generally, we expect the existing workflow validations to continue working as is.

Please create a support ticket and tag me in it, so we can assess what validators you currently have on your instance, and whether / how they can be migrated to use the "Parent" field.

Thanks,
Konstantin

[Paddy Walsh]

Hi @Konstantin Kulishenkov . Thanks for the answer. Not sure how to tag you on a Support Ticket but it is https://support.atlassian.com/requests/PCS-232049/.

[kyle.odoherty]

Hi there, 

When selecting a parent, is there configuration that can be made to give preference to items from the same project that the child ticket is in? 

Team is now finding when searching for an epic name it is returning items from many different projects as top results rather than items from the project the ticket belongs to. 

[Jan-Henrik Vogel]

Hello,

just a quick question regarding automation. On creation of Epics we used to use this code:

{
"fields": {
"Parent link": "{{ID}}"
}
}

If I change this to 

{
"fields": {
"parent": "{{ID}}"
}
}

i geht the message "data was not an object (parent)". What is the correct field name to update the automation?

Kind regards

Jan Vogel

[Chris Thomas]

I'm having the same issue as Megha Debnath.  Parent field is not visible in the Create screen.  I have added the field to the screen but it still doesn't appear.  

[Brian Lamb]

We are having the same issue as Megha Debnath and Chris Thomas.  Parent field is not visible in the Create screen.  The screen/field schemas show Parent listed, but when creating an OOTB issue type the Parent field does not show up.  We have a custom issue type, and the Parent field DOES show for this one.  But that is the only issue type that Parent shows for.

[HiRez Kitten]

So I've worked with this for a day so far, but I'm already not liking how entering a keyword in the Parent field isn't filtered to the current project you're working in. It shows all past project epics in our company with those same keywords, where as before it was easier to find an epic here since it was sorted by project. Hoping we can get that feature back?

[Cindy Haynam]

@Irene apologies if this was already covered in a previous comment - I scrolled through and didn't find the answer so its possible I missed it.

my question is if hierarchy is still enforced with this parent field? for example - if we have initiative --> feature --> epic --> story --> sub-task as our hierarchy, this isn't the hierarchy required in every situations. sometimes I may want initiative --> epic or feature --> story. I thought this might be possible with this new parent field but it doesn't seem to work this way. 

basically, i'd like to add any issue type above me and not be forced into the same hierarchy. Currently today since we're forced into this hierarchy, we create dummy issues. Was hoping this change would eliminate the need for this.

hope my question makes sense and thanks for your help :) 

[David Shaw]

@Cindy Haynam 

Jira Software has always supported exactly one issue type hierarchy. The unification of subtask link, epic link and parent lInk (from advanced roadmaps) into the one parent field has not changed that.

(For company managed projects, an issue at any level may have subtasks, if that helps.)

We are gathering interest in support for multiple issue type hierarchies and you could add your voice.

[David Shaw]

@Jan-Henrik Vogel 

It looks like your JSON is not quite right, ie. the "parent" needs to contain a "key" or an "id". So in your example, you would need to use:

{
   "fields": {
      "parent": { 
         "id" : "{{ID}}"
      }
   }
}

The REST API documentation has all the details.

[Konstantin Kulishenkov]

Hi @Brian Lamb and @Chris Thomas, thanks for reporting this to us.

Please refer to the public bug https://jira.atlassian.com/browse/JSWCLOUD-26109, which we use to track this problem.

It has the "Workaround" section with some details on what to do to temporarily resolve this.

Thanks,
Konstantin

[Annelotte]

We currently noted 3 issues and the change has rolled out just 3 days ago:

• parent drop-down does not show epics of same project at the top, this makes it almost impossible to find the proper epic if you are not familiar with the project
• jira filters that have the epic link column selected in the filter columns: It is not possible to hide the column, so you are stuck with it...
• The epic create screens shows 'parent' field and I cannot hide it by unchecking it in the menu under ... We don't use a higher level than epic in this project, and it is not a mandatory field.

I have asked our administrator to create bugs for each of them.

[Safak Gurhan]

Dear,

How can we write a query to search for tasks,subtasks linked to the specific epic through the stories?

[Florent Baret]

hello,

I would like to adapt all custom scripts using "Epic link" (=customfield_10006 universally) or "Parent link" (=customfield_10007 universally), by the new "parent" field and particularly in Scriptrunner Listeners.

But actually there is no Jira event for a Parent changed event, and Issue updated does not capture the Parent changing, only edition of "Epic link" and "Parent link".

I contacted Adaptavist but it seems they need first the "Parent changed" event be added first by Atlassian. Below is their answer. Could you made a feedback on this please ?

Based on the details related to the event available inside the listener, it is designed by Atlassian , and we do not have control over it. However, Atlassian allows users to create custom/generic events they need. However, generic/custom events will not work like the built-in event. I suggest contacting Atlassian regarding their improvement and any changes to the plans for the event.

[Sune Vester Lindhe]

Hi,

We have customers being affected by this as well - can it really be true that no event is fired when "Parent" is changing or are we missing something?

[Tom Solaru]

@Irene will this mean that Sub-tasks will behave like an Epic does with a Child Issue? It would be good if they were able to decouple but still have a parent relationship so you can have Sub-Tasks assigned to different Teams in their own Agile Boards without being tied so strongly to the Parent Task

[Irene]

Hi @Annelotte , thank you for raising those. 

"parent drop-down does not show epics of same project at the top" - we are looking to make improvements on this. Stay tune!

"jira filters that have the epic link column selected in the filter columns: It is not possible to hide the column, so you are stuck with it..." - please test this again. We have lifted the lock so you can hide the column now

"The epic create screens shows 'parent' field and I cannot hide it by unchecking it" - you can't hide it, but you should see this message and no issue will be returned in the drop down, that will stop anyone from adding any Parent field value. 

[Irene]

Hi all,
We are working on the issue where for some customers the new Parent field is not shown, while Epic Link and Parent Link are disabled (https://jira.atlassian.com/browse/JSWCLOUD-26109). For fast relief, please note the temporary changes we are making:

• Only customers whom we have rolled out the Parent field to, will temporarily now be able to see the Parent Link and Epic Link fields enabled again along with the Parent field. All 3 fields are writing data to the same source so there will be no conflicts
• If you were enrolled in our Beta group, the above doesn't apply to you because we haven't received any report of the same situation
• We still advise customers to continue using the Parent field in JQL, Automation, Workflow, or APIs. The issue doesn't impact the use of Parent field in those areas
  
  

Exception:

• JSM Customers should continue to use Epic Link and Parent Link as we are investigating a separate report 

[Irene]

@Safak Gurhan , you can use the JQL syntax of "parent =" to get all of that parent's subtask and child issues. What it won't give you is the child issues' sub tasks.

[Konstantin Kulishenkov]

Hi @Florent Baret and @Sune Vester Lindhe!

Just to confirm - is this about webhook events in Jira? The "issue_updated" event is fired when the issue parent has been changed, and it contains the "IssueParentAssociation" changelog item, that represents the "Parent" field. It appears there alongside "Epic Link" or "Parent Link". Refer to Change 6 from https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048.

This is what Marketplace apps usually consume if they need to react to the “parent changed” event.

Currently, the REST API and webhooks should already support the "Parent" field (while maintaining backward compatibility with "Epic Link" and "Parent Link").

Thanks,
Konstantin

[Florent Baret]

hi @Konstantin Kulishenkov ,

Thanks a lot, I was not aware of the new behavior and I was still expecting a field name "Parent" like in old behavior.

And particularly a "fieldID"="parent", as referenced by rest API. But if well understood, in the new behavior, the fieldID will be null when "field"= "IssueParentAssociation". So all is ok for me (and probably for @Sune Vester Lindhe too!)

Very clear and this change page is really a gem !

[Sune Vester Lindhe]

Hi @Konstantin Kulishenkov Thank you for the prompt reply! I can confirm as well that we do get the issue_updated event. The problems we were seeing were due to other things.

//Sune