Can I retroactively mark projects to use Shared configurations?

[Swift Capital]

Is there a way to do the following?

1. Create Project #1 with it's own configuration.
2. Create Project #2 with it's own configuration (sans Shared Configuration).
3. Retroactively apply a shared configuration of Project #1 onto Project #2.

This is concerning this new feature.

[Brent Webster · Accepted solution]

Hmmmm. All my workflow transitions have conditions set to control access. There is one transition that goes from "Ready to Submit" to "Resolved" and the conditions on that transition do not allow that user to fire it. There are no transition that directly go from "Resolved" to "Ready to Submit" but the comment above show that Anonymous did do it. I'm using three plugins: ScriptRunner 2.1.11, Subversion 0.10.11.1 and Universal Plugin Manager 2.11 which are all rock solid plugins. I appreciate your responses Nic but for now I'm just going to have to keep a watchful eye on the situtation.

[Nic Brough -Adaptavist-]

Your workflow is missing conditions, such as "only people in the role of user can do this"

A workflow transition with no conditions is executable by absolutely anyone who can see the issue, without logging in. That's what's happened here.

Have a look at the (uneditable) jira default workflow - you'll see it has no transitions without any conditions, there's always at least one enforcing a "user must be logged in because I need to know that they're part of role X"

[Brent Webster]

Good point but the active workflow does not have a transition directly from Resolved to "Ready to Submit" so how did it get there.

[Nic Brough -Adaptavist-]

It did when the user clicked it. Either that, or you have a plugin that is bypassing the workflow (I'd advise deleting that immediately if that is the case)