Hi @Georgino,
Depending on what you are trying to achieve, the best suggestion I could give you is: don't go there ... 😉
The epic link field is being deprecated and is (for some time now and largely) replaced with the parent field instead. This allow you to create parent-child relationships between issues consistently.
To create hierarchy levels above Epics (Jira's standard hierarchy on the standard and free plans is Epic > Story and all other 'standard' issue types > Sub-task), you would need a premium plan.
The Atlassian marketplace offers quite a few hierarchy / structure apps that allow you to define custom Work Breakdown Structures / hierarchies, but these usually leverage issue links to build these hierarchies, rather than trying to create something new for this.
Hope this helps!
I recommend @Walter Buggenhout 's suggestion of not going there. :)
Just replicating the field behaviour of epiclink will not solve all the problem as the other features around that field is inbuilt in other functions.
Best is to upgrade to premium and use the 'parent' field with the custom hierarchies or use plugins like Structure
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.