Marc -Devoteam- Community Champion

Still create an automation rule. Steps: * Trigger: issue created * Condition: reporter equals your account * Action: Edit field component and add the required admin component.

Hi @JC Toledo Welcome to the community. I mostly suggest to use components for this as labels are case sensitve and therefore no the most reliable. I use the following app that allows management of components globally in an instance. octo-component-version-subcomponents-and-sync-for-jira 

Hi @Marat Popov mail sent is always text or html as a global setting. If you want formatting in email you need to do this in html encoding. Wiki Style rendering setting on applies to the field used in the system, this formatting will not be used in sending mail. JWT has a special function for this. See the documentation…

Hi @Paz shwartz Welcome to the community. Contact Atlassian Support in relation to the topic. They can access your instance and probably remove the domain connection to the old instance or even help you get back into the instance.

Hi @Shabbir Salemwalla This earlier community post might give you some pointers in the right direction How-to-install-Assets-Discovery-Agent-via-SCCM 

Hi @Kirsty Parker Let them check if the Jira where the data resides is linked with the Confluence instance where you want to use the macro.

Hi @Kirsty Parker Welcome to the community. What is the Jira Plan you have, you require the premium plan to make usage of Advanced Roadmap (Plans) in Jira. This will allow you to use the Confluence macro. If you comply to this, I suggest to raise an issue at Atlassian Support, as this most likely is an issue with your…

Hi @Jyoti Mane Do you get an error, or else, can you show more information like screen shots. Macros configuration. Can you view the roadmap in Jira, so are permissions correct on the roadmap? To be checked: 1- Add Jira-users group to Advanced Roadmaps Viewer setting in Plans>Settings>Advanced Roadmaps permissions 2- Do…

Hi @Daniel Shukrun Correct, no brute option No as the directories are independent of each other. Also as the internal directory is always there on installation and you start from this before you can integrate and external user directory. Also be aware of the pointers I gave you around existing users, especially the admin…

So your JQL is the issue and I think this is baed on the fact the your JQL refers to a specific sprint. Sprint = Cyber, this sprint only exists in project EVO correct, not in other projects? So remove this clause and the future and closed as openSprints is the only. clause that requires to be true. JQL: sprint in…

So based on the log action. An issue was created in project NUM, the project is in the scope, otherwise the rule wouldn't have been triggered. The issue created NUM-20201 doesn't result in TRUE on the JQL condition, so the rule doesn't comply for issue NUM-20201 and therefore no action is performed. This is exactly the…

Hi, So I expect project EVO is in the scope. What does the audit log show on the no actions performed? Are all custom fields an or system fields you have a condition or action on in the rule available on the EVO project? And as the rule runs on issue creation, are the fields that are being set or edited on the create…

Hi @Gary McDermott You can use value "0" When I do this in workflows I always use factor 10 numbering. In your case as example: Add the opsbar-sequence property for each Status of the workflow To Do -> key = opsbar-sequence and value = 10 Awaiting documentation -> key = opsbar-sequence and value = 20 On Hold -> key =…

Hi @Daniel Shukrun This can only be resolved by comparing users. What is the main user directory for login, is this the AD group? Then it's most likely that the AD integration has been added later then Jira intro in the company and the internal directory has been used first, but probably has never been cleaned. Do watch…

Hi @Piskorz Magdalena (BD/BTM-IC1) No, it is not possible to customise the options for sorting child issues in an Epic at this time. You can track the following feature request: JRACLOUD-78353 

Hi @Green, Desmond I think you have the Table and Charts app installed as you mention formatwiki function. There documentation has information on this, see here I hope this helps you in your required direction. You could also reach out to their support in case, you might need more help.

No. The scope reflects to projects the rule is able to execute in. The scope is not that if an issue is created it will run on all projects int he scope. So if you create an issue in Jira, this automation checks if the projects is in scope of the rule and if this is Yes, the rule is executing. But depended on the rules…

Hi @Sergey Vasilyev Welcome to the community. Please reach out to Atlassian Support

Hi @David Stephensen Within your Atlassian Administration, go to Users and change the filter to the group Org Admin. Find the user usr you want to remove the permissions from., Select show Details and in select the 3 dots and select Remove organisation role.

But what I see here is and what will happen is: Rule is run when issue is created, then the scope is on play. It's immediately checked if this issue is in any of the projects defined in the scope. If this is true, the rule will run. But the rule runs on that issue in that project only. This is default behaviour.

Hi @Ayse Arslan For trail purposes, Yes, but I would read the privacy and security related details. This if the app stores any data outside Atlassian and where it is stored and security, this if your company has any GDPR related policy that doesn't allow to have data stored in specific locations, etc.

See documentation here on scope

Hi @Xavier Lenne Welcome to the community. Your thinking is wrong. The automation you made is used on projects specified in the scope, that does not mean that if the automation is triggered based on the trigger and conditions and actions specified in the rule So if an issue in one of the projects specified in the scope of…

Hi @Ayse Arslan This is not possible ootb, this would require and app from the marketplace to fulfil your need. See examples here

Hi read the documentation on the working of setting approvers, this can be done as by adding the field to the request and specify the approvers by default. Or the agents handling the issue can set the approvers or if you have the user field that you use for the approval on the request even a customer is able to set their…

Hi @Erika Smith There is, or there isn't. This is listed as a bug in automation. See the KB article on this topic; automation-rules-referencing-large-project-roles-fail-to-complete You can follow the Bug issue to, this is the issue: AUTO-1066 

That's means that you need to be the reporter, assignee or a watcher on the issue. The settings you presented initially, are you personal profile settings, this doesn't mean you get emails on any issue in the system.

Hi @Brad Wood As mentioned by @Kian Stack Mumo Systems This will always be customer facing as internal comments can only be made by an agent. An email sent about an issue needs the issue reference in the subject, this will be handled as an customer facing comment. Via the API you are able to place a comment as internal,…

Hi @Elvis Juan Espinoza Lope Approvals can be used on statuses within a workflow used in a JSM project. See how approvals work, in the following documentation: https://support.atlassian.com/jira-service-management-cloud/docs/set-up-approvals/ There is a default customer notification on a JSM project that sends the email…

Hi @Lakshmi Kumari What is within the notification scheme on the project, does this have notifications set on actions and are theses represented in the workflow(s) as well?