Marc -Devoteam- Community Champion

Hi @janez_m You need the 2nd option at least, with the keys. It might be an option to use, the smart clause flatten(), this should provide the output as a list.

Hi @Felix Kruszinski So JSM just doesn't have this option. But your statement, "Also if Users from Company X are not assigned any Organization and some failure is in Workflows and/or Security Levels, they can see Tickets from any other User from Company Z. Security? Save of sensible Data?" Applies in any application, if…

Hi @Mathew Lederman You cold look at the Multiple Help Center option. create-and-manage-help-centers I mentioned this, as you have tagged you instance a Enterprise. This option is to have some more customisation options for your Help Center

Hi @__ Jimi Wikman @Bill Sheboy is right in his knowledge, the same applies for an Asset object. If it's deleted, the attributes details are gone, you can reference the attributes used in the Asset you deleted. The same applies in relation to a work item, as described.

Hi @Harald Heinz This is not doable in a single rule, as the trigger of the rule is the sub-task. So indeed it's parent will be updated, as you stated, The Epic will not as the trigger of the rule is the sub-task, not the child of the Epic (Story, Task, etc..). You will need a second equivalent rule that triggers on the…

HI @Kevin Vancrutsen @Nikola Perisic is right here. Then you could create an automation after this action. That fires on work item creation and and set condition that apply, based on link type and then use the set Request Type action.

Hi @__ Jimi Wikman @Mikael Sandberg and @Bill Sheboy have a valid point. If you still want to use a read only field, there should be an option to compare. You would need to store the key of the asset in a variable and then you should be able to compare the variable value with the value in the read-only text field The…

Hi @Felix Kruszinski Welcome to the community. Issue Security can provide a solution for you. create-security-levels-for-issues In relation to setting this up create an automation rule or rules, that will set issue level based on the customer creating the request. This is not doable with the organization settings

Hi @Gestionnaire doublons Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request. This will help other community member trying to solve the same or provide them with a work around P.S. If the answer is very valuable to you, please share some kudos.

Hi @Guilherme Ventura Queues in a JSM projects are based on a filter, queues don't have permissions. If developers should not see certain issues based on a level, implement issue security. create-security-levels-for-issues configure-issue-security-schemes Otherwise if security levels don't fit you need, you could look for…

Hi @Janaina Oezcan I assume this client name mentioned in the summary field or description of the issue. If it's a text field add a condition in the automation, like;

Hi @Kevin Vancrutsen As @Julien GOURDEL mention, this can be set in the main template and by default this is set in the template ootb If you don't use the default customer notifications, but an automation rule, then this should be possible as well. Then you could use the smart value, {{issue.Request…

Hi @Dan Jackson You could implement this isn an automation rule, use the Manual trigger from Work item https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Manual-trigger-from-issue Then you can execute the automation only when required.

Hi @Tobias Bosshard Unfortunate their is no exclude option, only an include option. Best solution I can provide you is to add all users/customers that should no be able to raise this request in a new (to be created) group and add group to the request.

Hi @Ryan Wasson Welcome to the community. Check the permissions on the related structure or check with your Jira admin. Might be that permissions have changed on projects level or structure level, based on your account or even group that you are part of. Here in community, most of us are Atlassian users like yourself and…

Hi @Guilherme Ventura Can you elaborate your question? What would you like to lock, screenshot will help. Create separate queues, will be an option. Or use security levels based on an issue security scheme which level set will be visible to which group of users

Hi @Biswash Lamsal What I have found no, as this information is not stored at tempo side but at the Atlassian site. You cold contact Tempo with this question, if this is possible. Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request. This will help other community…

Hi @Jane D_ This should be the correct JSON according to the KB {"update": { "customfield_10047": [ {{#useraccountIDs.split(",")}}{"add": {"id":{{.}}}}{{^last}},{{/}}{{/}} ] } } But as this doesn't seem to work, might be worth contacting Atlassian Support

Hi @Ali Azzam Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request. This will help other community member trying to solve the same or provide them with a work around P.S. If the answer is very valuable to you, please share some kudos.

Hi @Shia Liu Then this option seems to not be in place anymore. You could raise a support request with Atlassian Support

Hi @Markus Schrotter Yes you can, but the chance you will find someone using this app is slim, and using the function that you specifically use.

Hi @Nachiket Bal Yes, people required to get in to the project settings, still see the People option, but all actions they take will not have any impact, as there would be no permissions based on a role in your permission scheme.

Hi @Jane D_ It could be my error. Can you try the JSON: {"update": { "customfield_10047": [ {{#}}{"add": {"id":"{{accountIDs}"}}}{{^last}},{{/}}{{/}} ] } }

Hi @Julina Del Rosario You will need to make sure this issue is already a customer and the email address is correct.

Hi @Nachiket Bal You can stop using roles in the permission schemes used on the project, base the permission schemes fully on groups and users. Then when in the people section a users is added to a role, this will have no impact at all, as no roles are then specified in a permission scheme.

Hi @Shia Liu Welcome to the community. The following might work, but you need to try this. * Identify the correct transition ID: you can identify the unique ID of the transition you want to execute. * Use the acli transition command. syntax to transition an issue: acli jira workitem transition --id <ISSUE_ID>…

Hi @Jodee Page On my side this works, with my summary seach terms. https://ayadev.atlassian.net/rest/api/3/search/jql?jql=summary~textA AND summary~textB You can even past it in your browser with the spaces, it will be replaced by html coding

Hi @Jo-Lee Bertrand I can't tell you there is no more information available, then the line I provided you. There is no mention if the For You page is defined on your permissions and your created boards. It just mentions boards, on my instance I see all boards under the section as I have access to all boards. I don't see…

Hi @Jo-Lee Bertrand For you: Get an overview of the things you care most about in Jira. Find work items, projects, boards, and queues you’ve visited, work assigned to you, and your starred items. If you require more information, I suggest to raise an issue with Atlassian Support

Hi @Nath On a renewal of you license you will always receive a new license key and SEN. This will have no implications on your running instance on a server. This is just information that is needed by Atlassian to validate the license.