Was wondering if anyone has opinions on the upcoming inline editing in jira 5.1. In a nutshell, you click on the field in the view screen, then edit it and press the tick or tab away. One of the big Atlassiguys told me that 90% of issue edits are single fields, so this makes sense. I guess editing fields in the issue navigator will follow shortly thereafter. One thing I'm confused about is if you edit two fields on the issue will it send two notifications? Presumably it waits a while then batches them in to one. EDIT, in the EAP at an rate it sends a mail for every field edited inline. Here's my concern. Organisations with complex processes need to validate multiple different fields in concert with each other. If you edit and commit one at a time, I don't see how that can be done. The new way of editing doesn't seem to allow for saying: if you set the due date you must also fill in the "reason for due date" field, or if you select country Mexico then XYZ option is not valid for field ABC. And I'm also looking at the amount of work required to make the behaviours plugin compatible, if it's even possible, and wondering whether I will discontinue it. BTW you can download the milestone release from http://www.atlassian.com/software/jira/download-eap - it's worth a look.

UPDATED 04/10/13: Code much cleaner now, but function needs to be called directly in the view template of the customfield to work. This is how it works for us: disableInlineEditForCustomField : function(customfieldId) { var oldEditable = JIRA.Issues.IssueFieldModel.prototype.isEditable; JIRA.Issues.IssueFieldModel.prototype.isEditable = function(){ return (customfieldId != this.id) && oldEditable.call(this); }; } We just disable customfields that should not be inline editable. To use this you need to execute the disableInlineEditForCustomField function directly in the view template of the customfield. It works quite good, still any suggestions on how to improve the code are appreciated :-)

Community
Answers Developer Questions
Questions
jira 5.1 inline editing... how this will work for you?

jira 5.1 inline editing... how this will work for you?

Viewing page 2 of 2

28 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes

+1 to be able to disable inline editing, If possible this should be possible at project level since i'm afraid enabling it on individual screens would cause confusion for end users.

Also user notifications must be sent for inline updates as well (at least i want this as default) else this will cause more end user confusion imho.

To make inline editing sound i think it should be possible to inline edit multiple fields and update them together with one click. To save the tons of javascript hacks around there should at least be an AUI function that puts a field into edit mode dynamically.

I really hope Atlassian comsiders this feature. Just support single field inline editing would be the wrong decision imho