Forums

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

Replicating JIRA Agile backlog in Structure Plugin

Matt Whiteman November 7, 2018

I would like to replicate the content and capabilities of the 'Backlog' tab from JIRA Agile in the Structure plugin. In particular:

  • Group by sprint (so I can drag and drop between sprints and the backlog)
  • Only show active/future sprints and the backlog
  • Order by rank

The contents of the backlog and each visible sprint should exactly match what I see on JIRA Agile.

I have got close to achieving this by:

  • Creating a structure which inserts all issues from the Agile Board (using the same filter) and groups by sprint
  • Creating a second structure which inserts the first structure, and then uses the 'Hide Closed Sprints' filter (which only works on inserted structures).

The problem is that if an issue was in a sprint, but is now back in the backlog, when I group by sprint in the first structure, it appears under the closed sprint, which means I can't get it in the backlog.

Replicating JIRA Agile's backlog in Structure seems like something a lot of people might have attempted to do, so was just wondering if anyone had been able to do this!

1 answer

0 votes
Vlad Lessage
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 8, 2018

Hi Matt,

Thanks for posting!

In order to better investigate this issue, could you kindly confirm which versions of Jira and Structure you are currently using?

I look forward to assisting you.

Best Regards,

Vlad

[ALM Works]

Matt Whiteman November 8, 2018

Hi Vlad,

Thanks for replying! 

My JIRA version is v7.4.4#74006-sha1:cbc13d9

For the Structure version, I'm currently using 4.3.0, but my team will be migrating to a JIRA instance that uses 5.1.0 over the weekend, so if the newer version has capabilities that will make this much easier, then we can assume I'm on the newer version!

Thanks,

Matt

Vlad Lessage
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 9, 2018

Hi Matt,

We did implement a fix for the Sprint Grouper with Structure 5.1. Please let me know if you still experience issues once you start using that version.

With that said, in order to get the desired results, you can go about this 2 different ways:

A. 
1. Apply the Group by Sprint Generator to your current structure
2. Apply Transformation: Filter by Sprint - Hide Closed Sprints ( you must filter on "current level")

B. 
1. Create a new, empty structure
2. Insert your current structure into the new one. Please note that your current structure must already have a Grouping by Sprint. The reason for this is that Filters are executed before Groupers, as you may have already noticed. (So if you insert your structure, add the Sprint Grouper and then apply the Filter, nothing will happen. )
3. Filter: Hide Closed Sprints (make sure to filter on "current level")

I hope this helps. Please let me know if you have any additional questions or if you need further assistance.

Best Regards,

Vlad

[ALM Works]

Matt Whiteman November 13, 2018

Hi Vlad - thanks for getting back to me on this. What you've said makes sense if the sprint grouper has had some fixes in Structure 5.1 (I assume the fix is to put items that have been in previous sprints in the 'Backlog' grouping too if they're still in the backlog?).

I haven't been able to test this yet as the migration to our new JIRA instance with Structure 5.1 didn't happen as planned,  but as soon as I can, I will test, and then Accept your answer if it works!

Thanks again,

Matt

Vlad Lessage
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 13, 2018

Hi Matt, 

No problem at all, happy to help.

The issue regarding moving items in Closed Sprints to the Backlog has technically been fixed since 4.5 actually. However, we further improved the Feature with the release of 5.1. I anticipate you'll get the desired results as long as you keep in mind the order of the Generators as previously described. 

Thanks for letting me know, I look forward to hearing back from you after you update Structure.

Cheers,

Vlad

[ALM Works] 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events