Hi, we are currently evaluating the Structure plugin and it looks really good so far. It provides an easy way to add, manage, and visualize tasks. We have a few questions about its integration with another Jira plugin: Jira Agile. * When I reorder items inside Structure, will it also reorder the items inside the Agile Board? * Apparently I can reorder stories and tasks, but Structure doesn’t allow me to reorder sub-tasks. Is this a limitation or a misconfiguration problem in my instance? * When a new task is created, it goes to the Agile Backlog. Is there any way to execute an action to move the task to the current Agile Sprint? Again, the plugin is really awesome. If the things mentioned above cannot be achieve in the normal way, is there a workaround, another plugin, or any other thing that can help us achieve that? Thank you! -Martim

Hi Martim, Thanks for using the Structure plugin and for the great feedback! In order of questions: * Absolutely, you need to set up a JIRA Agile synchronizer - it will keep issue rank in your Structure board in sync with rank in your Agile board; changes made in one board will be synced to the other. It will also synchronize Epics > Story relationships in both directions too. * Could you expand a little on this one - do you mean that Structure won't let you reorder sub-tasks in the Structure board? Can you not move them at all or does it let you move them then they jump back to where they were? Can you re-order them within their parent issue? If you are trying to move them to another issue and you have a synchronizer running that forces sub-tasks to stay under their parent issues (both the Sub-Tasks and JIRA Agile synchronizers can do this), this would prevent you from moving them to another location (i.e. placing them under a different issue to their biological parent) in the board (they would jump back to where they were originally), but it should not stop you from re-ordering them within the bounds of their parent issue. * There's no standard mechanism for this in Structure, but you could add the Sprint column to your Structure view and specify the required sprint ID when creating the issue. You need to configure your JIRA to add the Sprint field to the issue editor screen, otherwise it won't be editable in Structure. I'm not sure about automating the process - when you say the current sprint I assume you mean the current active sprint? This may be possible with scripting at JIRA level. Cheers, Robert

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Couple of questions about Structure integration with Jira Agile

Martim Schnack

Hi,

we are currently evaluating the Structure plugin and it looks really good so far. It provides an easy way to add, manage, and visualize tasks.

We have a few questions about its integration with another Jira plugin: Jira Agile.

When I reorder items inside Structure, will it also reorder the items inside the Agile Board?
Apparently I can reorder stories and tasks, but Structure doesn’t allow me to reorder sub-tasks. Is this a limitation or a misconfiguration problem in my instance?
When a new task is created, it goes to the Agile Backlog. Is there any way to execute an action to move the task to the current Agile Sprint?

Again, the plugin is really awesome. If the things mentioned above cannot be achieve in the normal way, is there a workaround, another plugin, or any other thing that can help us achieve that?

Thank you!

-Martim

Accepted answers

Robert Leitch [ALM Works]

Hi Martim,

Thanks for using the Structure plugin and for the great feedback!

In order of questions:

Absolutely, you need to set up a JIRA Agile synchronizer - it will keep issue rank in your Structure board in sync with rank in your Agile board; changes made in one board will be synced to the other. It will also synchronize Epics > Story relationships in both directions too.
Could you expand a little on this one - do you mean that Structure won't let you reorder sub-tasks in the Structure board? Can you not move them at all or does it let you move them then they jump back to where they were? Can you re-order them within their parent issue?

If you are trying to move them to another issue and you have a synchronizer running that forces sub-tasks to stay under their parent issues (both the Sub-Tasks and JIRA Agile synchronizers can do this), this would prevent you from moving them to another location (i.e. placing them under a different issue to their biological parent) in the board (they would jump back to where they were originally), but it should not stop you from re-ordering them within the bounds of their parent issue.
There's no standard mechanism for this in Structure, but you could add the Sprint column to your Structure view and specify the required sprint ID when creating the issue. You need to configure your JIRA to add the Sprint field to the issue editor screen, otherwise it won't be editable in Structure.

I'm not sure about automating the process - when you say the current sprint I assume you mean the current active sprint? This may be possible with scripting at JIRA level.

Cheers,

Robert

All comments

Robert Leitch [ALM Works]

Hi Martim,

Thanks for using the Structure plugin and for the great feedback!

In order of questions:

Absolutely, you need to set up a JIRA Agile synchronizer - it will keep issue rank in your Structure board in sync with rank in your Agile board; changes made in one board will be synced to the other. It will also synchronize Epics > Story relationships in both directions too.
Could you expand a little on this one - do you mean that Structure won't let you reorder sub-tasks in the Structure board? Can you not move them at all or does it let you move them then they jump back to where they were? Can you re-order them within their parent issue?

If you are trying to move them to another issue and you have a synchronizer running that forces sub-tasks to stay under their parent issues (both the Sub-Tasks and JIRA Agile synchronizers can do this), this would prevent you from moving them to another location (i.e. placing them under a different issue to their biological parent) in the board (they would jump back to where they were originally), but it should not stop you from re-ordering them within the bounds of their parent issue.
There's no standard mechanism for this in Structure, but you could add the Sprint column to your Structure view and specify the required sprint ID when creating the issue. You need to configure your JIRA to add the Sprint field to the issue editor screen, otherwise it won't be editable in Structure.

I'm not sure about automating the process - when you say the current sprint I assume you mean the current active sprint? This may be possible with scripting at JIRA level.

Cheers,

Robert

Martim Schnack

Hi Robert,

first of all, thank you for your quick reply.

Here is more a more detailed exxplanation of the problems I am having:

0) Initial configuration doesn't reflect Jira board

Structure Syncs Settings: https://db.tt/ptyc5HVf
Structure x Board - side by side: https://db.tt/xtARGsCr
As you can see, the Stories are not inside the Epics.

1) Reordering Stories inside Structure doesn't reflect in Jira Board

I've organized the Strcuture, but the Jira Board looks the same: https://db.tt/AVFbVG7p

2) Reordering Sub-Tasks not working

I reorder the sub-tasks inside a Story, but after a few seconds, they switch back to the original position: http://screencast.com/t/KQcd4xC83

I'll try adding the column for the Sprint.

Thanks!!

Martim Schnack

Robert,

apparently adding the Sub-Task filter was causing the issues mentioned above. I've created a new Structure with only the Filter and Greenhopper syncs, and everything works.

I'll keep you posted about #3.

Robert Leitch [ALM Works]

Martim, you beat me to it!

I'm glad you got that sorted, looking forward to the update.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

structure

addon-com.almworks.jira.structure