Improvement: project role and issue type based re-planning permission

From the Planning Board view, it's possible to drag and drop a card into a release to change its fix version.
However, in our organization, only a few persons (product or dev managers) are allowed to change the content of a release for key features (ie. selected issue types like New Feature or Improvement).
We have implemented this control rule into the Jira workflows in order to make sure this key management rule is respected.

The GreenHopper behavior is breaking this configuration, allowing anyone to change a release plan. This is a show stopper for us.

It should be possible to configure permission like "give re-planning rights on {issue type} cards to {project role}".

Without that, I'm afraid we'll have to post-pone this cool plug-in deployment.

Vince

This is a pretty neat idea vince.
I don't think it will be that hard to implement also. I will submit this improvement but I cant say where it will end on the priority list.

Can I ask you how you managed/implemented your workflows ?

Thanks again Vince

J
C
H

No problem.

In our process, the Improvement and New Feature issue types are under a strict change control ruling. From a Jira perspective, only Product or Development Managers can technically assign one of these issue type to a fix version.

In order to change the FixVersion of one of these issue type, you must go through a single transition that has the adequate single view where the fix version is editable.
Only Product Managers and Development Managers have access to this transition.

Some other issues types (the "derived" ones - Stories, Software Requirements,...) have a different, lighter change control ruling and some other roles (Analyst, PM,....) are technically allowed to propose new fix versions for them.

I hope it's clear

Would you have any more question, please let me know.

Vince

Ok so here is what I understand:
1- You removed the fix version field from the default screen.
2- You added a Transition with a screen that has the fix version but this transition is only accessible for some groups/users

Pretty clever.

I have submitted this behavior improvement and the reaction was pretty good. Now lets hope it will be implemented soon

Thanks Vince, I really appreciate your time and interest for GreenHopper.

J
C
H

Thanks to you.

I demoed your plugin to a bunch of product/project managers here and they were very excited with it.

I just want to make sure the current limitations will be addressed before taking a commitment on a deployment in our production instance.

I'll keep you informed with my investigation work.