Marc -Devoteam- Community Champion

Hi @Seenivasan K That information is in the history of the issue as well. But you can create an automation rule that based on field value changed. Do an edit action and use the advanced option. See, example: { "update": { "customfield_10055" : [ { "add": { "accountId" : "{{assignee.accountId}}" } } ] } }

HI @Andrey Ivanov How to fix them is stated in the warning and error message. Values need to be added on components. And on some request type in the project the Approvers field need to have applied a value as the field is hidden on the request preset values of the users granting the approval need to be set. The links on…

Hi @Natalia Bakos Then an admin changed the status name and type, but not do this on a workflow, but in the System -> Issues -> Statuses configuration in the Jira System Settings.

Hi @Lisa New If you are referring to Scrum related projects, than this is not possible. The Epics will not show intermixed with the child issues in the list of issues in the Backlog screen for a Scrum board. You can, however, display the Epics in a pane that will display between the navigation pane on the left and the…

Hi @Natalia Bakos It seems someone cloned a workflow and edited this workflow as it was not assigned and renamed a status in the workflow. Statuses are global in Jira so renaming a status impacts this status name used in any other workflow in the system

HI @Ivana Janeková Welcome to the community. If you manage your own subscriptions with Atlassian and not a partner or re-seller. You need to have the org-admin permission, only org admins can modify these settings. If you don't have this role, only another org-admin can grant you this role.

Hi @Berik Irgebayev Yes, that will exactly happen.

Hi @Adrian Szubert Can you show example issues, as notification are triggered via email or as user being assignee, reporter or watcher. @mention is a single notification, cloning via cloning option or via an automation rule should not keep @mentioned user notified. What kind of notifications are the @mentioned users…

Hi @Seenivasan K What is you exact request? You have a custom assignee field, what type of field is this, user picker, multi line text? Can you show you complete automation rule and the log of the rule execution? This will all help community members, your current attachment only show part of a rule.

Hi @Adrian Szubert Are they the reporter of the follow-up stories or are they stated as watchers or are the issue linked or is it in the workflow, what is the case? What kind of notifications are they getting? Also what does the automation look like, is it somewhere in the automation that they are related to the follow-up…

HI @vincenzo.spatafora Then crate a variable first based on the custom field and then the edit. Then use the variable instead of the {{issue.For Information}} or {{issue.customfield_27200}}

Hi @mark.liebold Can you show screenshot of the automation you have setup. This will help community members to get an insight in you way of thinking and the setup.

Hi @Jeramy So your admin project is also JSM project. So any user with a JSM license, who is able to access other JSM project is able to see internal and external comments. This is not dependent on the Service Team role. It is based on the license.

Hi @vincenzo.spatafora Yes the Edit action and select the multiline field But add : {{issue.For Information}} or {{issue.customfield_27200}} {{issue.comments.last.body}} The first smart value is to retina the original content. Check which smart value you need to retain the original field value the name or custom field ID

Hi @CGSoto Contact Atlassian Support in this case to have them check the logging of you instance

HI @vincenzo.spatafora In you automation rule, select the field where the comment needs to be added. place first the smart value {{issue.,name of the custom field}} Then add extra line (enter), twice. On the second new line set the smart value {{issue.comments.last.body}}

Hi @Wally David Welcome to the community. You would need to create an automation rule. * Use the trigger Issue Updated, Use the Assignee field * Use create variable action Name the variable (I used partofsummary in my example) Smart value to use: {{issue.summary.substringBefore("-")}} * Use Edit issue action Select the…

Hi @Bryan Henderson This is a case of process. What do you define as a process to you consider the Story done if it meets the DoD If you use testing in the Story (development) and this is part of the DoD and this fails, then I would adhere to raise a Bug and leave the Story open till the Bug is fixed and the Story…

Hi @Peter Nikolajsen Are you referring to moving pages in the sidebar of your space? I tried this on my end, and if a move a page to another location and the move somewhere else in Confluence and revert to the space, the pages is where I moved it to. You could try another browser and/or clear your cache and cookies in the…

Hi @Tomislav Tobijas I tried the app you mentioned, but I found this more looking to the person and not company. But that's my take on it of course!

The apps that I like to use are: * draw.io * checklist for Jira pro * JMWE * Optimizer for Jira * Custom Charts for Jira

The apps that I like to use are: * draw.io * checklist for Jira pro * JMWE * Optimizer for Jira * Custom Charts for Jira (Confluence)

Hi @Andrew Renault Create a custom field of the type single user. If you want that user mentioned on all updates on the issue, you can create a custom notification in the notification scheme used by the project The custom notification should be set on the custom field created and choose the notification you want to have…

Hi @Samadhan Sawant Welcome to the community It might be you are running in to this, see: https://github.com/serverless-nextjs/serverless-next.js/issues/984 I don't think it's Xray API related.

Hi @Abhishek Tiwari Ask you IT department, who manages Jira. This can't be seen in the system

Hi @Changlin S There are no options to create custom fields that can be managed by non-admins. Even apps that can add custom field options, need to be managed by a Jira admin

Hi @Jaewoong Choi @Salih Tuç is correct here. But if you are on Server/DC, so the latest version is 2. (tags on the issue) Jira DC/Server Platform API - https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/ 

Hi @sandeepgowda0047 Welcome to the community. Please search the community on this question. It has been asked many times Is the Final Status in the Final workflow of you sprint board the final status of the used workflow? If not, within the scrum template in Jira an issue is not considered burned in the sprint and on…

HI @Jeramy JSM Customers don't see internal comments, unless you have granted them an agent license. So if they see internal comments something is not correct in the permissions on your JSM project.

Hi @ribas No your request is not feasible. Why is this a concern, status are unique yes, but you can use this status in any workflow. What is the reasoning to use prefix for example like an status called "Open" A status is not bound to a workflow a status is an building block to be used in a workflow. It is also best…