Have another Issue Type like an EPIC

[Gor Greyan]

Hi, Dear Community,

We have the following situation.

I need to have an Issue Type, which will be under EPIC but will act like an EPIC.

We need to have that EPIC, under which we should have some design tasks and should follow the progress of those tasks via the EPIC.

Would like to see any suggestions on how I can achieve that.

[Nikola Perisic]

Hello @Gor Greyan 

Since you are on DC, should be the same for the cloud which is issue hierarchy where you would include more issue types to be on the same level as Epic. Example:

[Gor Greyan]

Hi @Nikola Perisic

Thanks for the information.

But will these issue types work like EPIC?

Having Epic name and child issues?

[Nikola Perisic]

@Gor Greyan 

They will work as Epic, since they have the hierarchy of level 1. If you have a child issue that needs to be a part of the Parent field, you would also need to include the work item type in your work item type scheme of the project that you are currently using in order for the relation to be relevant.

[Gor Greyan]

Hi @Nikola Perisic

Thanks a lot.

Will check and get back to you.

[Gor Greyan]

Hi @Nikola Perisic

I have added a ticket in the Epic hierarchy level.

I have created a ticket with the Epic Name field, but in another ticket, when I entered the Epic Link and wrote the Epic's name, it did not suggest that Epic.

Please see the screens.

 

[Nikola Perisic]

Hi @Gor Greyan 

Instead of Epic Link it needs to be Parent because Epic Links will be deprecated.

[Gor Greyan]

Dear @Nikola Perisic

I could link it via Parent Link, but I want the child issues' estimations will be visible also in this Parent.

Now it is not visible.

How can we also do that? 
Like in the Epic, Summary Panel.

[John Funk]

Hi Gor,

Epic Link, Epic Name, and Parent Link have been deprecated. Please use the Parent field. In the Parent field for the Epic level, it would show values from the Project/Feature issue type level in Nikola's example. 

[Gor Greyan]

Hi @John Funk

Thanks for the answer.
But couldn't find the Parent field.
With the Parent name, we have only this fields.

[John Funk]

Sorry about that - didn't notice you were still on Data Center. So what is the problem with using the Parent Link? 

[Gor Greyan]

Hi @John Funk

I could link it via Parent Link, but I want the child issues' estimations will be visible also in this Parent.

Now it is not visible.

How can we also do that? 
Like the Summary Panel, which is visible in the Epic.

[John Funk]

Not understanding that you want the child issues' estimations to be visible also in the parent. What does this mean? That you want the total of the child estimations? Or that you want the individual child values - which is not possible. 

[Gor Greyan]

Hi, Dear @John Funk

See, for the default Epic issue type, I have a Summary Panel section in the right part, which shows how many tickets are completed under that epic, estimation and etc.

For the new Epic level issue type, I couldn't see that information.

See the attached screenshots.

[John Funk]

Yes, I believe that Jira has programmed functionality on either the Epic naming convention itself, or on that particular work type ID. I do not believe you will be able to mimic that functionality with other work types at the same level. You should probably open a support ticket with Atlassian to find out what they are really doing. 

If you do, and get an answer/solution, then please post back here with guidance. Best of luck!

https://support.atlassian.com/contact/#/

[Gor Greyan]

Hi @John Funk

Thanks a lot for the answer.

[Gor Greyan]

Hi  Dear @John Funk

One question also :)

I want to set automation so that when my Design task goes to Done status, the issue in the Parent Link goes to "In Progress" status.

In the automation, for the branch I set Epic(parent), but the Parent is not being recognized as Parent :D

Do you have any idea?