Work Item Hierarchy Field

This is such a simple concept but a total game changer for some of our stakeholders - especially as we're in full on 2026 planning mode. So being able to see the ancestry of tickets on the screen itself is a huge win (we have 3 levels above the out of the box Epic). There was an initial issue with rendering icons for non-standard issue types which I reported back to Dave - and given this is a side project he's been really responsive and helpful to get a fix in. I switched the field back on as soon as I got notified of the fix on friday and a couple of my key stakeholders spotted it within minutes - and commented how useful it is. Thanks for spotting the gap in the base product and coming up with the solution for it :-)

I gave you a four star rating because I think that the idea behind this is excellent. Especially because on DC I used to build this Feature with the single issue picker custom fields manually. Since there seems to be a lack of commitment from the company to develop this further I would like to help and push this internally so this idea gets the well needed attention and budget. Very much needed for people who have a well structured hierarchy. Wish: Make custom issue type pictures load, too :) Thank you for providing this app free and making Jira Cloud more useable. UPDATE: It works for me- showing custom issue type icons - thank you so much for making that work, Dave! It looks awesome in my project!

• 

  Atlassian Labs

  Thanks for your kind words Marleen - that's much appreciated. This is a side-project so I'm only able to work on it in between regular work, so I've unfortunately not had a lot of time to dig into the issue with custom issue type images, and so far I've been unable to reproduce it on my instances which makes it had to ensure I've got a fix - I will try and resolve this though!

  - Dave (app author)

The Hierarchy field did not appear immediately after installation. After an hour or so, I noticed that it had eventually been added to my custom field options. When adding to an issue screen, at first it doesn't seem to do anything; there's just a blank next to the field. If you keep the issue open for a few minutes, it will show "Loading..." then display the parent. It seems slow and the graphics break. I'm not sure if this will be any more useful than the default Atlassian breadcrumbs on the top of issues.

• 

  Atlassian Labs

  To a certain extent these are all fair criticisms and I do appreciate the feedback. However, it's worth bearing a few things in mind in terms of the context... firstly the field won't be added automatically, that's not possible - you need to choose which work item screens you need to add it to and the instructions to do this are included in the Support section under documentations (see https://draperd.atlassian.net/wiki/external/ZGQ4YTgxOGJiM2VjNDg1NDg0ZWU0MWUzMWZmYzMzZjU )

  In terms of the loading time, this is restricted by the lack of APIs to fetch all ancestors and the speed at which they run as well as the number of ancestors that a work item has. The application needs iteratively request each parent as it "walks" the ancestor chain, so the more ancestors the longer it takes. There is also a general lag with any Forge custom field as it is not included in the main server side render (due to technical limitations).

  There is a known problem with some broken images in Forge apps and its regrettable this is happening here. This shouldn't occur with regular work item icons, but can occur with custom icons that have been uploaded.

  So whilst this criticism and feedback is both fair and can be a valid reflection of the application experience, it will not be case for all experiences so I hope it doesn't deter other users. I've received additional feedback on the broken image problem and I'm trying to find a workaround for it.

  More than anything I do appreciate the feedback, even if constructive / negative because it gives me something to work with an reveals problems that I hadn't experienced when testing on my own available instances.

  Thanks for taking the time to provide this information. I'll try and resolve these problems as best I can and feed these up to the relevant teams.