Hello Art,

Sorry about that, we're still catching up on the documentation.

To insert a structure into a structure:

1. Enter Automation Editing mode by clicking "Automation" button.
2. Select the parent item, under which you'd like a structure to be inserted.
3. Click "+" near the Automation, select "Insert...", "Structure...".
4. Pick the structure to insert and click OK.
5. If no other automations are required, click Automation again to exit automation editing mode.

Hope this helps!

Kind regards,
Igor

I see that this has been implemented in 3.0 and the release notes say a new feature is "structures within structures", but I can't seem to find any documentation as to how to add an existing structure to a new structure.

Hello Sarika,

If I understand correctly, you'd like to tie a structure to a specific project. Unfortunately, that is not currently possible (except limiting the structured projects globally). May I ask you to create a new idea for this feature? This specific issue is not relevant.

Also, if you have any questions (rather than ideas), please send them to support@almworks.com.

Thanks!
Igor

hello all can u suggest me one thing about structure plugin.in my jira system have 20 project and 20 structure, and when i create issue in one structue the project list show but i want perticular project is lock for that structure.

Hello Ruedi and all, we're closing in on Structure 3 beta, which will have this feature. The beta version will be available soon - sign-up available at http://almworks.com/s3/

Kind regards,
Igor

Hi Igor, any news according to this super nice and helpful feature?

Hi Kostas, still working, getting close! No decided date yet, sorry.

Hi Igor, any updates on a release date for Structures v 3.0 by any chance?

Hi Angell, still working on v. 3.0! Sorry, I know it's taking a long time, but it's a huge release. Check back in 2015!

Igor, what is the status of this now?

Travis, this feature is being developed, but we don't promise the dates of a release. I suggest that you base your purchasing decision on what the plugin can do for you at the moment.

Feel free to write details about your requirements and what you need to achieve to support@almworks.com - we'll try to suggest the best way to implement it using the current version.

Igor

Is this feature still being developed? We're considering buying the plugin, but this is something that we'd really need. We have multiple teams all with projects where one team may have a task in another team's project. For example, the IT team is deploying a new platform, they have 30 tasks, 2 of the tasks are for the Development team. The Development team also has those same 2 tasks in another project that has 30 tasks, etc.

Thanks for your comments and I have an update on this: we're going to do this! Our current focus is Structure 3.0, which is expected to have all there's needed for including one structure into another.

No ETA is available at this moment, sorry.

Igor

Ideally we can grapht a part of someone elses structure onto our own (readonly)

Pete, thanks for the explanation, it is clear now.

(Btw, you can configure your settings to automatically receive an email when a topic you participate in is updated.)

Sorry for the late reply, I don't look here very often...

Say I have two products A and B, A is made up of IP blocks 1,2,3 And B is made up of IP blocks 2,4,5

You can see that Both products share IP block 2.

I would like to have an individual structure for each IP block, and Parent Structures A and B, which can then import the IP structures. And any shared structures are identical and changes reflected across both projects. (just now we can import or clone structures (I think), but then they become independent)

This means that teams working on Product A can see any progress on IP Block 2 that has been done by the team working on Product B.

So the two project structures would look like

Product A
IP1
issue1.a .... etc.
IP2
issue2.a
issue2.b
issue2.d
issue2.c ..... etc
IP3
issue3.a

Product B
IP2
issue2.a
issue2.b
issue2.d
issue2.c ..... etc
IP4
issue4.a .... etc.
IP5
issue5.a

Any changes in IP2 would be refelcted in both products A and B, i.e. they are the same structure not a copy, nested within a parent.

Pete, thanks for your comment! Could you please elaborate, what do you mean, "having the issue locations in the substructure replicated" - having a single issue multiple times in an overall structure?

I'd like to see this too. We would like to define work on individual system components in terms of a structure, and be able to see add that structure in multiple other structures that represent different systems.
It would be useful to be able to show/hide different tasks related on filters, and also to have the issue locations in the substructure replicated.
We can achieve a lot of this using filters and synchronisers, but it takes a lot of careful setup and isn't quite right

Reason in our Case would be different teams Räson

Sounds good, thank you for the consideration.