Marc -Devoteam- Community Champion

Hi @Romy Meyers This is possible, by using a different permission setup in the internal project. You permission scheme used be adapted to only use groups/users, as roles in the system are global any user with a JSM license can see any issue in a JSM project if the role Service Team has been granted the browser project…

Hi @Jarrod When using a KB you need to start using labels on the pages in the Confluence KB space. You can limit per Request Type which articles will be shown, based on there labels. There are no differentiators based on combination of permissions possible. See documentation on KB's…

HI @Nick Whiteley Welcome to the community. In your new schema create an object attribute on your objects to reference to the service objects in the ootb services schema. This is your way to go as the ootb services schema can't be configured

Hi @v.d.thangavel Welcome to the community. I'm not sure this can be done, but you can read this documentation on rate-limiting https://developer.atlassian.com/cloud/jira/platform/rate-limiting/ 

Hi @王芳 Welcome to the community. 这是什么类型的项目，基于您提到文件夹的问题（Jira 没有文件夹）。 您能否分享更多详细信息，例如屏幕截图？ 您的问题似乎与 Jira 中使用的 markeptlace 应用程序有关。 如果是这种情况，最好联系应用程序的供应商/开发人员。 或者向 Atlassian 支持部门提出支持请求。 https://support.atlassian.com/contact/ 这是 Atlassina 社区，产品爱好者在这里帮助其他用户，但这不是官方支持

Hi @Tri-Sang Vo What docs are you referring to and what macros can't be used. What do you want to place in a comment using automation? Whenever you ask for help with an Automation Rule it will help us to help you if you provide: 1. what type of project is this (e.g., company-managed, team-managed, etc.), 2. images that…

Hi @[deleted] This is not an option. The app starts using data the time its active in your instance. You could reach out to the apps vendor/developer, to see if there is a solution they can provide.

Hi @Aire Vaigu Welcome to the community. Remove the autogenerated SLA if you don't require it or change the JQL in the Goal of the autogenerated SLA or the priorities that are set.

Hi @Miroslav Šestak What are the fields configurations and what are the customer permissions?

Hi @TMonatisa See this post on the developer commuinty. https://community.developer.atlassian.com/t/missing-public-name-field-in-jira-rest-api-user-endpoints/73537 It's also best to raise question on development on the development community

Hi @Magda Szrajer So this is the reason Free Tier subscriptions don't have this option Please accept my answer as a solution, if my answer helped to solve your request. This will help other community member trying to solve the same.

Hi @Antonia This is not a status, but a resolution. Adjust your workflow and add a post function to the reopen transition and choose the update issue field post function, select the field resolution and set the value to none.

Hi @Antonia Do all the issues have a resolution set, JQL all your issues and add the column Resolution to the results. Is there information in there?

Hi @Magda Szrajer I should be in the feature setting, add the bottom, in the labs features. I can still see this, I only mis this option on the free tier instance I also have. So that could be the case, are you on a free tier?

Hi @Sarah Bizewski You would need an app for this, the one mentioned by @Kate Pawlak _Appsvio_ will do so. I personally find it bad Practice as people could try to find information on the assignee and try to reach them each time on getting there help on raised issues, even not assigned to that person What is the business…

Hi @Ian MacDonald I still have the option in the Issue List from the project, so it could be your instance.

HI @Ian MacDonald I have never seen this before. This could only be the case if there is separate transition to the same status without a screen.

Hi @TMonatisa Welcome to the community. The User management REST API provides resources to administer and edit managed accounts. So this is to manage users that are managed by an IDP. So I don't think you can use this in an app. This because you are not in the position to manage the IDP endpoint. Even if there was an API…

Hi @pbaldwin Welcome to the community. Contact your ORG admin, find the users who started the Cloud instnce.

Hi @Dimitrios Kouroumichakis Create a Team, add all HR members. Set the Team field as with preset value on HR requests made on the portal. Then you could search on all issues where team = HR

Hi @Martin Vali What if you (based on the last screenshot) set the branch on "All created issues"

HI @Dimitrios Kouroumichakis Ootb there is no option to show additional fields on a JSM Portal. You can explore the marketplace for app that provide such a functionality

Hi @Dániel Vincze Welcome to the community. Most of the permissions in the permission scheme do't apply to customers. Edit/Delete comment or attachment don't apply to them for instance. Also see the ticket provided by @Sebastian Krzewiński in the Atlassian public Jira.

Hi @MdV There are no permission for this. It's not possible via bulk edit, see the related issues in my previous reply. Atlassian will not implement this. The only option you can explore is to run an automation rule that finds the issues based on the JQL you have and then on branching iterate over the found issues, to…

Hi @Jasper Hovenga What type of. request s raised and what is the queue's filter set to. Could there be a mismatch Are there any automation rules running on issue created, may they change options so that the issue will appear in the queue? Do those automations take up a certain amount of time, if so overlook the automation…

Hi @Pavel Rusakov Yes remove the role mapping the permission schemes. The will make the "add user to a role" button useless, as no roles will be specified to permissions in the permission scheme

Hi @Amit Kumar Singh Setting a default value for a field does not result in the value being set for issues that already exist. The default value is applied only through the Create Issue screen.

HI @Bogusch, Matthias Welcome to the community. This sounds like a bug. I suggest to raise this at Atlassian Support (https://support.atlassian.com/contact/) If they resolve this or classify it as a bug, can you post the result here?

Hi @André Matzke Clean your browser cache and cookies, or try incognito or another browser.

HI @avi.paghadar Welcome to the community. If you have calls that require the experimental option (stated in the documentation), it's best to use an API tool. Doing this via the command line usually gives these kind of erorrs.