You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hey @Jason Lewis,
Unfortunately there is currently no way to add or manage other users as watchers on the new issue view. This is something we plan to support in the near future.
If the new design currently doesn't meet your needs, you can go back to the old view by clicking "See the old view" in the top right or by switching the feature off in your user profile (click the ••• on the issue and click "Turn off new view").
Also, if you have any feedback for the team you can click the "Give feedback" button in the top right. We read this daily and use this to inform what we build and improve next.
Hope this helps!
Thanks for the feedback, feel free to send any other specific feedback that you might have too. We're working hard to improve the new design as we build more functionality, features and address feedback we've received so far. Rest assured, we won't be rolling out the new design permanently until we've delivered the features, functionality and improvements that have been driven by the customer feedback we've received so far.
We just figured out that using [~username] to tag is not working in the new issue view.
My instance has some specific restrictions which prevent some users from using @name to tag someone for security reasons, so they had been relying on the [~tag] to get this done.
I've instructed them to turn this new view off for now.
It would be nice, as an admin, if I could have an option to opt-out of trying new features that pop up without warning. I don't mind so much this happening in our test boxes, but it can be frustrating in production instances.
Rest assured, we won't be rolling out the new design permanently until we've delivered the features, functionality and improvements that have been driven by the customer feedback we've received so far.
I received a notice today stating that the ability to turn off the new Jira experience will be removed within the next two weeks. The new Jira still does not give me the ability to add my team members as watcher's on tickets though.
This functionality is critically important in our world.
My colleagues and I have submitted feedback on this and other items via the "Give feedback" button for the past couple of months, to no avail - at least this is what it seems like.
@kai This is a very critical piece of functionality to remove. As with many companies we have leads and developers that work under them to assign issue types to. We need a way using JIRA Cloud to be able to add the leads as watchers (or even Product or QA team members) to tickets so everyone is aware. When will this be available for JIRA Cloud?
I'm a long-time JIRA user (15+ years) and must say that the new view right now seems like a grossly unfinished product that is not ready to be given to end users at this point. There is simply too many features that are not present and it's too laborious to explain to novice/infrequent users how to turn off the new view to return to the old.
As mentioned earlier in this post, adding watchers is a critical task to easily add people to a ticket. However, there's lot of other features that aren't present that we use -- all critical. Please consider getting rid of this 'new view' until more functionality is present, or allow an Administrator update the system to revert to the old view.
- my team has hit the same problem:
- ie., we seem to have lost the ability to manage and view watchers in the new view
- this is core functionality and we can't believe it has disappeared in the new views (its one of the reasons we loved using JIRA since it enabled team members to keep each other in the loop on relevant issues and to quickly check who was a watcher on a given issue)
- the new views are therefore unusable for my team without the ability to independently manage and assign watchers
- in May you mentioned that "Rest assured, we won't be rolling out the new design permanently until we've delivered the features, functionality and improvements that have been driven by the customer feedback we've received so far."
- its now September and you seem to be rolling out this new view while still missing this required functionality
- can you give us an update on when we can get this functionality back?
- i've had to waste time this past week responding to questions from my team because this new issue view was rolled out automatically without the required core functionality
- if you can provide an update that would be much appreciated
For those watching this topic, I worked around this (somewhat clumsily) by getting a free add-on from the market place that allowed me to set up my projects so that users are added to all issue types automatically.
It's not ideal - like using a nuclear warhead where a scalpel would do, but it at least ensures me that my users are tracking / aware of new issues.
@Jason Lewis Atlassian has heard and responded - this feature is available in Cloud:
If you can see the View Watchers iconbut not the + Add Watchers, then check your project permissions. You will need the "Manage Watchers" permission.
Just my two cents. Watchers is a critical feature of JIRA. Atlassian you need to get over that you made a mistake by removing it from the "New-View" and just find a way to put it back in.
Switching back and forth between "new" and "Old" view will probably go away as another "Enhancement" from Atlassian.
As a blogger GeekMustHave.com I have been asked by my readers about JIRA. I was a total fanboy and helped others get started with JIRA. Now, I can't with a good heart recommend JIRA.
Listen to the people in the posts and others like it. Put "Watchers" back in.
Agreed, and with a 9 month turn around from first report to date, I concur it is a matter of Product Manager will, not Technical difficulty that is preventing the feature from being restored.
Can the “New View” be considered successful if users have to abandon it to do their work?
This has been in the backlog for 8 months and I still have to search and find an answer for this when one of my users turned on the new view by mistake. I turned the new view off months ago because it is completely useless.
Please do not change things just to change them. If you change something use feedback to guide your hand. Its very clear that the "new view" is not being driven out of necessity or user will.
Managing and viewing watchers is very important for us, +1 for adding it soon, and would like an update on timing.
It's hard for us to switch to the old issue view because we need certain functionality related to subtasks that the old issue view does not provide, but we really need manage watchers as well.
Our team was manually switching to the old view every time we have to Manage watchers on a ticket. Not sure if there is a way to stick to the old view from within JIRA settings. (please suggest if there is one).
For now, have written a tampermonkey script to do this, others might find useful. - https://openuserjs.org/scripts/chitwan.malhotra/JIRA_-_auto_redirect_issue_to_old_view.
Try clicking lower-left avatar/icon and select profile, scroll to "Labs" and unselect "New Jira issue view". Sometimes I find I have to clear the session storage in chrome for it to take effect. I think there have also been times where the setting somehow got reactivated and I had to unselect it again.
I am surprised people are still complaining about this. I was one of the original posters that reported this issue. It has since seemed to be resolved. I switch back and forth between the new and old issue view and they both now have the ability to add watchers.
Note: I am using Sofware projects and am NOT using NextGen projects. I don't know if the issue view is different for NextGen projects and if the problem still exists for those.
Atlassian Team - This has been an issue since 2018! What is the hold up in adding this critical functionality back? Our workflow requires leads and managers to be able to view tickets in their respective areas which we can easily define in Jira, but we cannot add them as watchers. I have no idea why this was removed and I have yet to receive an answer from Kai... he no longer seems to be with Atlassian.