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?
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.
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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Trello is one of the most effective tools for driving your sprints. It's customizable for every Agile team and product owners and Scrum masters (SM) love it. However, Agile teams often struggle with:...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs