Change to details view update

[Lynn Squire]

There was a recent change that my  users don't like that I want to reverse but can't seem to find a way to do it. A couple weeks ago the following message started showing to my Service Desk users "We've collasped your details and activities view to help you focus on the work that matters most." the result is the collasping of the detailed view. My users want to see it, How do I change it back?

I tried to adjust it by having them turn off the "JIRA LABS" option in their personal setting but that didn't help. As a JIRA ADMIN I don't see this view. 

Please help? 

Here is an example of what I am talking about (notice along top)

[Earl McCutcheon]

Hello @Lynn Squire ,

This change was rolled out in response to an overwhelming amount of feedback we got after we released a previous change to the activity feed ordering and comment boxes, where many customers were frustrated at that time with having to scroll to the bottom of their requests to get to the latest comment.

Our aim with having the request details and the activity section collapsible and minimized by default will mean less scrolling and easier access to the comment box, with the option to expand as needed to see additional details.

So From your description it sounds like your primary concern is that you would like an option to have the default setting so that the details view could be expanded by default rather than collapsed as rolled out with the new feature, is that correct, or did you have additional thoughts on this?  Let me know and I will put together a feature request based on your input for follow up.

And just for a bit of clarifications in the feature, currently the changes applied are that there is now a "Show details"/"Hide details" button. Clicking this button causes the details panel to expand and collapse. When the details panel is collapsed, only the reporter and creation date fields are shown. When the details panel is expanded, all field values are shown. Prior to this change, all field values were always shown. When a request has a request type that has no fields, only a summary, then the "Show details"/"Hide details" button does not appear as there is nothing to show or hide in this case.

The Default settings are set so that if there is a Connect app installed that injects UI elements into the details panel, then the panel is always expanded by default to prevent conflicts with the add-on apps access to the visible fields and the following rules would not apply in that case.  But if no apps are installed that inject values or elements to the page and the request has zero or one activity items, then the panel is expanded by default.  If the request has more than one activity item, then the panel is collapsed by default.  Even when expanded or collapsed by default, a user can still toggle the section to expand or collapse at will.

Regards,
Earl

[David Lopez]

Under the use case of viewing comments this change makes lots of sense. But, if you are looking for Approval it adds an unnecessary step, and will not be intuitive for users that aren't in this all the time.

Adding the ability to choose the default setting, or adding access to the use custom logic would allow greater flexibility. Or something like "On First View" show details.

For our Change Managers, of course, they get access to the whole system, but for our Approvers that are Executive or Director level sponsors of the Requests this would be super confusing (see image)

[Earl McCutcheon]

Hey @David Lopez ,

Thanks for the additional feedback and I have created the following request based on your comments and the original feedback from @Lynn Squire to track interest in changing this behavior:

• https://jira.atlassian.com/browse/JSDCLOUD-9024

Please make sure to add a vote to track your interest in the feature as covered in the "Implementation of New Features Policy"  and if you have any additional feedback points or suggestions about this feature, please drop a comment on the request, it helps out a lot.

Regards,
Earl

[David Lopez]

@Earl McCutcheon Thank you for doing that.