Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Edit issue (multiple fields) in new issue view - a workaround

Since the EDIT button has been removed and we can now edit all fields directly in the issue view we have been struggling with getting too many "issue edited" notifications. While this "in-view" edit is fine for small/single field changes it's not ideal when changing multiple fields at the same time.

As a workaround we have done the following and I thought I share this here in case you have the same challenge:

1. create a new screen (e.g. "<project>: Edit View") and add all fields you wish to edit

2. create a new transition in the workflow (from any status to itself) which uses the newly created screen as the transition view.

If you need to make this transition available in certain status only or restrict it to certain users, you may want to add some conditions to the transition.

I hope this helps!




@Thomas , did you get a better workaround? I am stuck as I want to put a validator that makes sure that a status transition is accompanied by a compulsory change of assignee field.

I just tried to switch to OLD VIEW permanently to specifically get around this issue of a jira going out for every single field that's changed. After I saved it, I was given a message OLD VIEW is going away the end of this month, 4/20/2022. That is a huge issue. I can't believe Atlassian expects every user of their system to use the above work around to avoid emails as well as all the other host of issues not having an EDIT button/view has (like not being able to edit fields that don't have data when it's created, and other things people brought up in Jira . It was started in 2018 so they've known about these issues a long time. June 18th 2021 someone commented untenable and there is nothing after that in that Jira. I just added a comment to try to raise awareness of it asking not to shut down OLD VIEW until they provide an edit view for online.) This is frustrating. Has anyone seen any updates for Edit View coming for this before end of this month when they shut down Old View? Or found a more reasonable solution than every user programming their own work around? Thanks!


Log in or Sign up to comment