This has been very problematic for our team. We put in about 2 weeks to a month planning big feature tickets, we use all the cool authoring tools like expand/collapse and warning messages. However once the ticket is ready to be worked, it not usable. For example, a dev goes to copy a color value out of the ticket so they don't have to retype it which increases the chance of error, but they end up in edit mode, all the expand controls expand in edit mode and they have to scroll the big document to find the spot to copy paste, thus defeating the purpose of that authoring tool entirely. One partial solution would be to make the expand collapsible in edit mode. Jira and confluence operation should fairly identical, we copy from confluence to create tickets when verbiage is ready. Confluence has the explocit edit button because the programmers understood our reading and authoring are so different, usually 2 completely different users in different roles. Another issue pops up when we are planning the subtasks for a story... we started using expand collapse because to set all the fields and content for the subtasks became tedious, everytime you backout of a subtasks and return to the parent, your taken all the way back to the top of this huge story and are forced to scroll 1 to 6 pages to enter the next subtasks. Thus, this "feature" presents a serious usability problem for both "planning" and "completing" work. Scope does change so we don't want to lock editing... but bottom line, edit and use/read mode are two different things and we find ourselves in the wrong mode by accident too often, edits occur when they shouldn't and use mode is, well, unusable.
I cant submit a feature request for some reason or vote for similar, and most of the equivalent threads failed to state the problems this causes, so I thought I'd try this.
