Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Biggantt - Setting up Tree Structure automatically

Rahul Mittal
Contributor
March 19, 2019

Hi,

In my organization, I have the below structure

 

JIRA PROJECT 1  -- has EPIC & STORIES as issue types

JIRA PROJECT 2  -- has FEATURE, BUG, IMPROVEMENT as issue types. 

 

And, we have a linkage like: EPIC -> STORY (linked via EPIC link in template)  --> FEATURE (linked via "More" and "Link Issue".

 

Now, in the biggantt chart, we get automatically the tree structure for EPICSTORY as they have proper link via JIRA template but FEATURE doesn't fall automatically under STORY.

Could anyone advise how that can be done? Currently, it is double work for me to first create the FEATURE and link STORY while creating ticket and, then go to Biggantt chart and move the FEATURE ticket under STORY using arrows..

 

Thanks!

1 answer

0 votes
Ijon Foden
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 23, 2019
Hi. I have similar problem. Did you find the solutions?
Rahul Mittal
Contributor
May 23, 2019

Hey, Yes... You need to set the "Task Hierarchy" under "Synchronization" tab.

image.png

Ijon Foden
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 24, 2019

Thanks Rahul. I checked it and it is works, but not always. I have a few questions more.

1. What is a different between linked issue, dependent and cloners? Are they different kind of dependencies?

2. In my Jira I haven't such many elements on this screen. I see only first three form left panel and first three from second panel. I see linked issue and cloners too, but not more. Why I have not them?

3. What's mean "lock parents" options?

4. WhatsW mean "inverse" option?

 

I will be thankful for answers 😀

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events