Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Cannot place anything after a dynamic row in structure Edited


2 answers

To configure this, you can do a manual adjustment:

Looks like this question fall under my radar, sorry about that, Manish et al,

Let me provide a bit of an extended explanation here. Dynamic rows in a structure are those created by the Automation. Automation is a set of rules and within these rules, you can only move issues that comply with these rules. So you can put a story, task, etc under Epic, provided you have Stories under Epic extender in your structure, but you won't be able to put an epic under epic this way. Though Linked issues extender will allow any type of hierarchy if needed. 

Now, generators are something you can never put under a dynamic row, as these are not issues and cannot have links themselves. Ditto folders. Ditto memos.

However, people often need to adjust their dynamic structures in small ways, for reporting purposes, for what-if analysis etc. So we have introduced Manual Adjustments. These can let you put almost anything in a completely different hierarchy. Which is fine, until you really need to find something in its expected place in the structure. Manual Adjustments allow you to defy the rules, but Structure here is to visualize these rules primarily and Manual Adjustments can defeat its purpose.

That's why we recommend not to use Manual Adjustments in structures many people use on a regular basis, but only apply them to make final touches to a report, do what-if analysis, or otherwise work with Jira hierarchy privately and occasionally. The final decision is up to the customer of course, but just a word of warning, powerful tools can let you make powerful mistakes.

In cases when you need only to change the order of your issues within a branch level, you can use Automation - Sort By>Manual Reordering. Which will not let you break hierarchy but allow you to move issues up or down a row for prioritization for example.

Egor Tasa

ALM Works

Do you have a release for when this will be in the cloud version as well?

No promises here, Nathaniel, as Cloud API is much more restrictive than server one. We plan to implement as many features from server version into cloud as possible, but when it will happen is not a certainty. You can subscribe to our cloud new here: and view our Roadmap here: (Note that manual adjustments are not there yet)



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - April 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

310 views 3 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you