Hello Jamie,
I notice that you managed to find a way around the inline editting thingy in JIRA 5.1 and up.
Currently when an issues has one or more behaviours, all inline editting is disabled for that issue, correct?
I have a global behaviour that applies to all issues in all projects.
It contains only two fields however.
So the current implementation of the jira behaviours plugin disables inline editing for all fields for all issues.
Would it be possible to limit the disabling to only fields in the behaviour(s)?
Or will this cause problems with dependencies?
Thanks,
Valentijn
Jamie,
I'd like to second Valentijn's suggestion:
A solution could be to configure the list of fields that should have inline editting disabled. Per behaviour.
This would be very helpful/useful for use and it would also prove to be an adequate solution for the dependency problems you mention.
Jeff.
Hi Valentijn,
Yeah correct. I guess it would make sense to only disable inline edit for fields with behaviours... I don't know about dependencies... Let's say field B is readonly unless field A has a certain value. So only field A has a behaviour applied. With your proposal you could edit field B inline. Unless you added a dummy behaviour for field B as well, which I guess would be the way to handle this situation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was thinking about those kind of dependencies, but it looks you can't configure those in the plugin?
Even if we couldhave such a dependency, the plugin could detect that dependency?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have to write code for that kind of dependency yes, but that's a primary use case.
> Even if we couldhave such a dependency, the plugin could detect that dependency
Nope... I don't see how.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, those damned groovy scripts;-)
A solution could be to configure the list of fields that should have inline editting disabled. Per behaviour. Or globally if easier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.