Kishan Sharma Community Champion

Thank you @Daniel Eads for the response, that explains the behavior, i noticed it and was able to repost after some time. 

Hi Rakshit, can you share the JSON body you are sending with your request?

If you are using REST API, you need to use the DELETE method on the watchers resource to remove watchers from an issue. Have you tried it ?

Glad to know Liam :)

Hi Vincent, You are right, I have just tested few things here. You need to use v3 API. refer below - https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post I am able to extract the issuetypes fields with below endpoints. eg:…

The like counter has worked now :), the comment on discussions counter still has issues it seems.

Thank you @Alexander Pappert I just replied Suvradip about it, I raised this here because I couldn't see votes button on my question earlier, but now i can see it, seems like someone has a magic wand :-)

Thank you @Suvradip Paul for taking a look. This was one of my question, earlier I couldn't see the Votes button, but i can see it now ;) do you believe in magic ?

@Christine P. Dela Rosa You have conveyed it so rightly!

Here is my post !

Yes, certainly not enough as there are many more elements that can be considered :)

Hi @Anand Have you tried Jira Service Management ? I think it will be more relevant to your use case. Read about it here

Some great updates, thank you!

Nice to know about these useful features, thank you for the demo!

Today, i can see the challenges, so one of the point from above can be striked off :)

Thank you for bringing up new cleanup features for DC, will definitely make it easy for busy admins ;)

Go get them all Atlympians!!

Hi @James Burdett you can give a try to below workaround - * Favorite/unfavorite the affected filter. This will flush the caches and the filter will be reloaded correctly. * Share the filter only with groups/users that have permission to view the projects in the filter

Thanks Stephen for confirming. If you have Edit issues permission in the project and if the field is added in edit issue screen, you should be able to change it as per your liking. You can check permissions in Project Settings -> Permissions.

Hi @Stephen Roberts welcome to the community. You won't be able to rename the system field or did you mean you want to change the text added by the customers in Summary field?

You are not alone @Suvradip Paul i am facing the same issue since morning! Even the points tracker/feed was freezed for me, but it has started moving now.

Thank you @Christine P. Dela Rosa for these effective points, I can relate to it. The work life impact play is great. In my past organization, few of the things that our leadership tried and worked wonders, listed below - * Gather feedback from employees via surveys * Created Employee recognition programs where individuals…

For me, the feed has stuck now, any tips ?

Thank you for the supplement Christine!

A bit late to the party, thank you atlassian team for providing this much needed feature.

The user base is definitely one of the reason, well articulated points @Benjamin Horst , thank you!

Like everyone suggested, we should have a process to gather requirements from users like why a new custom field is required, its purpose and whether an existing custom field can be re-used before creating a new one.

This is not working for me, even after leaving group /rejoin.

This is not working for me, even after leaving group /rejoin/refreshing the page. No such luck!

Rightly said @Ignacio Aredez That's what happens when employees burnout!