Hello, we're going to be showing a preview of Structure 3.0 at Atlassian Summit. If you are going to be there, stop by our booth and we'll give you a personal demo! A public beta version is planned shortly after.

Thanks everyone for your patience!

Kind regards,
Igor

Hello, Is there any update on this feature request?

Yeah, sorry about miscommunications about 2.9. The point was that we're developing 3.0 with all speed possible and we didn't plan to release further 2.x versions except patches.

Although version 2.10 is a next 2.x version it's not much different from a patch - we had to add compatibility with the latest JIRA and make some minor improvements. There were no new features, all new development effort goes into 3.0.

Although we can't yet promise a release date for 3.0, I can say that this version, which is more like a new, revamped product, is starting to converge. Please bear with us some more!

Kind regards,
Igor

After the release of 2.9, the 3.0 would come which includes the described functionality... In the meanwhile already a 2.10 exists... When is the 3.0 (or the desired functionality) coming?

Hi Frank, yes, it does!

Does this (upcoming) feature imply that we will be able to use a Link synchronizer to display an issue with 2 linked parents in a structure? Currently, the Link synchronizer will automatically remove a link to the parent when adding a link to another parent.

Hi Doug,

Thanks for your interest. Our team is currently working on 3.0 in full force (after the release of 2.9). As usual, we don't promise dates, but we won't be releasing any new versions besides patches now until we release 3.0. And this feature will be included.

Please stay tuned.

Kind regards,
Igor

Any updates on a 3.0 release and support for this issue?

Mark, thanks for your interest.

This feature is going to be a part of Structure 3.0 along with tons of great stuff. We're currently working on it.

We usually don't promise dates for the new features, but I can give a "negative estimate" like before - it is yet very unlikely that Structure 3.0 will be released in the following two months. It's not an estimation of the remaining work and it doesn't mean that after two months pass, Structure 3.0 is going to be there. But we'll definitely be closer to the release and I may have an update on this.

Cheers,
Igor

It has been almost 2 months since the last update. Can you give us a revised estimate?

Thank you for creating a very useful plugin.

Best Regards,

Mark

Jakob, there's no update yet, sorry. I can only say that we've started working on it and it's not going to be delivered at least in the two following months.

Hi,

Can you share any update on the time plan for Structure 3 and this feature? We are evaluating the plugin at my company and we see this feature as an enabler for us to adopt Structure.

Best regards
Jakob

Hi,

A very helpful feature, for my department having it will mark the difference between using or not Structure.

Thanks, we will wait for Structure 3.

Thanks everyone for your patience. As I mentioned earlier, this feature requires an overhaul of the whole product, otherwise it would have been completed already. Currently we're gathering such features in a separate pool and designing the new architecture. The result is likely to be Structure 3.

At this stage, we can't provide an ETA yet. It is most certain that this feature will not be ready in the next 3 months.

Kind regards,
Igor

Hi, any schedules for this feature? This would be really great to have a feature which an issue across multiple hierarchies within the same structure.

A feature like this would help in dependency management. We would expect to have several customer issues all dependent on the same development issue if they all find the same bug.

I see the need with different clients, this would be a huge benefit to the plug-in! I am looking forward to have that implemented as soon as possible.

Oh yes. Thanks for posting this. We have had similar requests already. This is something we'll be looking into a bit later because it would be a large overhaul of the whole architecture of the plugin. Certainly after version 2.0.