Hi Jira Team, I'm currently looking for a way to have some fields moved to the main left section body of the issue modal screen instead.

With several additional custom fields, the screen becomes very right side heavy which requires a lot of user scrolling.

Unable to render embedded object: File (Jira Customize Issue Modal Fields placement.png?fromIssue=3463343) not found.

Jira Team, This is a big issue for my Team, Since I create templates inside my custom fields, and thanks to this issue, they are not being displayed on Issue detailed view.

My customized bugs and stories don't have a Description field on that view because I cannot edit this view.

Please fix this issue

Jira team, what are you doing! I don't think this is a rare use case - you developed a custom field that allows teams to make paragraph sized fields, and then you stuck all of them in a tiny right rail. This isn't a viable solution, dudes. You gotta fix this one. 

"I don't care for this change, because moving the acceptance criteria to a less visible place, and making it so narrow that people have to do a lot of scrolling to read it is non conducive to getting more done."

We are now getting the same issue and while I accept that there is an update above, it's from August last year so I think another update is due. Of the issues raised having the ability to move some fields to the main view (rather than the side panel) would be a big win for the new view. I have to admit, until that happens I have gone back to the old view and will advice our users to do the same. 

I may look at the alternative - which is to remove our User Story and Acceptance Criteria fields entirely with a view of forcing users to make use of the generic description. 

presumably, if WYSIWYG type of configuration for the editors will become available, one would not only get a chance to define a fields list (or order), but also the way how particular field is to be displayed, including the area size, so hopefully as @tpechacek pointed above, we would get control over this critical functionality

my main question is "when??"

@Theo Levine - I think we all got hit with that UI change. Seems like now they want to make this new view the default view for issues, even when not viewing from the backlog. I don't care for this change, because moving the acceptance criteria to a less visible place, and making it so narrow that people have to do a lot of scrolling to read it is non conducive to getting more done. What it's going to cause is people getting less done, because while more may get done, it will likely not be done as per the acceptance criteria, and as such will require more time to go back and fix it. Because if people have to scroll around, especially below the page fold, to read something, it's a pretty safe bet they're not going to read it. They're going to carry on as if it doesn't exist until someone points it out to them, and even worse if no one happens to point it out until whatever it is has found its way into Production.

I just got hit with the UI change that hid the acceptance criteria on the right side of the page in a tiny scroll-able window - this is a serious problem for getting anything done despite Jira claiming "We're updating the issue view to help you get more done". I really hope this ticket exists to fix that and becomes a high priority, I need my AC front and center. 

Hello,

I agree with all the comments. For reference for your Jira IT team, i opened a ticket with my experience return and practical example, please see JST-412858.

We (and many users i think) really need be able to order and group fields, and as you say havin the possibility the position some fields on the main screen (large texte) for some of them (with for them too having the possibility to order/group) will be great too.

It will allow us to tailor the screen to our developpers needs.

Like Jonh Price say it very well, we are happy to have new from the progress of this issue. Thank you very much to you Taylor (and Jira team). It is very important to keep trust and confidence. I hope you will update this ticket regularly to keep us informed.

About transparency, i agree too with John. You should have a dedicated page with Roadmap feature, like Temawork do it (please see: https://www.teamwork.com/roadmap), i really like and it make me confident in the product. It's a simple page but it is so valuable for us! More and more compny play the transparency with users and it is really benefics for both side (see Gitlab, when they lost customer data, they put live videos on their office so from internet all Gitlab user can follow the issue, you cannot make more transparent). You should go this way and make us more informed.

What yould be nice is the possibility to switch on/off new feature by administrator globally for all users and choose which feature (not all labs on/off, but per new feature being tested against us). I think many people will see better the way you release/forcethe changes.

Could you please give us an approximative date when the possibility to configure filed order and group will be available in Cloud version please ? (1 week, 2 week, one month, 2 month...), just to have some visibility. I know you cannot give an exact date or engagement, but just to know it un-officialy an expected date/delay just for information.

Thanks,

Best regards,

Thomas

Taylor, thanks for this great info.  This is the sort of concrete update that I can take to my users and that shows that you guys do read the comments.  My background is in product dev, so I am usually able to talk annoyed users off the ledge with a combination of:

• You can turn off the new view for now.
• This is how all major product dev is done now - Gmail is not going to wait till the new inbox is "done" to roll it out.  They roll out a basic RC that meets needs for many users and then gather feedback.  

What would really help us a lot in general is:

• More insight into the roadmap for the new UX and other features, like "we're hoping to overhaul how the dashboard gadgets look in 2019".
• Advance warning of major cloud updates and some options to opt out.  Like "Your instance will get the new issue view beta on or around August 3, 2018.  Here's what to tell users."  We have 1800 users on Cloud and another 2000 on Server and though Cloud is the nicer offering, I miss the ability to review update notes at least a little before my users ambush me.  

I'll pass your notes on.  Thanks!

Hi everyone, I want to give a quick update on this issue. We are actively working on this feature and I believe we will be able to resolve almost all of the issues you have raised so far. I personally apologize for the frustration you are feeling around this, we hear you, and we are working hard to make this a really enjoyable experience for you and everyone on your team. 

• You will be able to manage the ordering of field layout in the new issue view. This will be a per project --> issue type configuration setting.
• john.price2, we are working hard to bring in the multi-line custom text fields into the content area. We initially treated all fields the same and put them on the right-hand context side, but we have received feedback that there are clear examples where Acceptance Criteria, Environment, and other fields of this type actually help describe the issue and need the wider screen space to convey the meaning behind that content as it can be quite rich/long like description. It will also come with the new editor for the awesome WYSIWYG capabilities.
• jelam894060335 We hear you on that and we are working to bring tabs into the new issue detail view.

The new issue view is not rolled out to all customers, we are still learning & iterating on a few things. Overall though we are feeling really confident in the new design and a large majority of our customers are really enjoying it so far. 

Configuration in Jira can get complex quickly and it is taking some time to wire everything up with the new issue view, as the configuration was built for a different design / information model.

If you have any other feedback that has not been raised yet, please let us know. We actively use these channels to inform our product decisions.

Taylor Pechacek

Jira, PM