We are currently trying to improve our Jira workflows by the user of the behaviours plugin.
Our first attempt is to lock down issue fields an make them writeable only for specific users. The problem that we encounterd so far is that we can not make
It seems that this is a common issue to the plugin at the moment? Can anybody please confirm that or suggest a workaround?
Well what we try to realise is:
- set a specific issue type in our project to read only for allmost all users
- other issue types should be handled normally by the users
e.g. We have a issue type "initial requierements" which can be viewed by all project members but only 2 admin of the project are allowed to change them.
We have set a field set a behaviours for every field in that specific issue type which set the field to readonly except you are a specific user. This works so far for every field exept the 3 named earlier.
I'm not sure if this can be done with scheme permission, since we have this readonly based on issue type?
Oh and yet another problem with this approach.
We have allowed inline editing of our issues. When we click on Edit Issue everything works fine
when we use the inline edit feature we have very different outcomes depending on webbrowser and webbrowser version :-/
With IE8 the read only feature does not work at all for inline editing.
In older FF Version (19) it has some delay and if you are quick you can edit the issue before it is set back to readonly.
We have seen the following error in e.g. IE8:
JS Error (yellow triangle left bottom of browser) Syntax error, unrecognized expression: hover batch.js Code: 0 Line 4 Char: 14659
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
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