Fazila Ashraf Community Champion

Hello @Mathias Nielsen If you actually meant the workflow status change trigger button i.e., transition buttons, have a look at the opsbar sequence mentioned in https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ 

@Vijay Racherla , do check the logs as Nic mentioned and the validators and postfunctions as Fernando highlighted. Just sharing my experience on why i have seen this exact error in my env.. When an admin plugin like scriptrunner, jmwe, jsu etc's license expires :( You could find more info in the logs.. If not, i would…

Hi @[deleted] Can you check whether there are any automation in place that does this? Check for your automation for jira rules and also scriptrunner listeners, postfunction and behaviours if you use scriptrunner in your instance. If you use any other automation plugin, do check on them accordingly. Also checking on the…

Hi @Tima K JSM do not have built in features for these integration but you can look up in the atlassian marketplace for 3rd party apps that can provide such features. I found https://marketplace.atlassian.com/apps/1225688/jirbee-jira-and-telegram-bot-integration-notifications?tab=overview&hosting=cloud that could support…

Hi @Manju Echoapps360 Welcome to community! Please have a look at the permission schemes of the projects to which the user is able to access (undesired). The browse permission might be available to 'Any logged in user' or group jira-software-users or any other groups or application access that opens up the project to a…

Hello @NGATDev Post the upgrade, does the normal jira notifications get triggered? Can you check the mail queue also?

Hello @Sebastian Pichler Welcome to community! The ability to include the component lead as recipient in the email notifications is native to JIRA application. Refer to https://confluence.atlassian.com/adminjiraserver/creating-a-notification-scheme-938847330.html for more information. Let me know if you are looking for…

Hello @SHANAVASH MOHAMED The below works for me.. Can you try and then extend it for your usecase?

Hi @Rich Wolverton Could you check whether there are existing automation in the project or globally that could cause this override?

Hi @Susana Méndez Welcome to community! In the automation library of the JSM project, you will find the below template which would help you configure the rule easily Do try it and let me know if you still face any issues.

@Meytal BM , like mentioned earlier, only users with agent license can see the agent related features like queues.. If you do not want other users to see your tickets, just look at the 'Browse issues' permissions and add only the 'Service desk agents' role there and manage that role's users in your project only to certain…

Hi @Meytal BM Only users with Service desk agent license be able to use the JSM features like SLA, queue etc. These other Jira s/w licensed users would behave as collaborators - (see : https://support.atlassian.com/jira-service-management-cloud/docs/what-are-user-types-and-roles/ ) You can simply update the jsm project's…

Hello Manoj Not sure whether it is intentionally different. Atlassian support https://support.atlassian.com/ is the right place to raise bugs and suggestions.

Hi @nilesh rokade Welcome to community! The details about the default statuses that are packaged in JIRA are described in https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-statuses-priorities-and-resolutions/ Accepted For recruitment projects, this indicates that the candidate has accepted the…

Hi @[deleted] Have you tried the solutions listed in https://support.atlassian.com/atlassian-account/docs/email-address-verification-issues/ ?

Hi @amit_bakst Check whether the workflow has the workflow properties that denies editing the ticket in certain status. Specifically, the properties jira.issue.editable or jira.permission.* could cause this Refer to https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ for more info

Hello @Ngoc Le Have to ask, so did you troubleshoot for all the causes that were listed in https://confluence.atlassian.com/jirakb/troubleshoot-a-jira-server-startup-failed-error-394464512.html ?

Hello @Kristian Lannu Welcome to community! Data residency is available for Standard, Premium, and Enterprise cloud subscriptions and Australia is available as a region. Refer to https://www.atlassian.com/software/data-residency and https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/

Hi @nicolaspannetier The error says that the rule has project restrictions. Is the Epic in a different project? Can you adjust the restriction in the 'rule details' section as mentioned and check?

Hi @Pandey Pradip 1-How is backup/Restore handled in Atlassian Cloud? For Jira and Confluence Cloud, Atlassian utilises the snapshot feature of Amazon RDS (Amazon Relational Database Service) to create automated daily backups of each RDS instance. Amazon RDS snapshots are retained for 30 days with support for point-in-time…

Hi @Shubham Burghate I cant think of a way to restrict assignment as being assignable is a project level permission. Why dont you handle these 3 groups in 3 different JSM projects as the agents are different? That might simplify everything..

Hi @Jerry C Paul Could you explain the user case? It is not possible to assign colors to the jira tickets but you could use JSM queues to look at the unassigned tickets in the project.. See https://support.atlassian.com/jira-service-management-cloud/docs/what-are-queues/

Hi @Drishti Maharaj By default the linked issues are independent and status of one doesnt impact the other. However, you can customize like 'do not resolve if linked issues are not resolved..' etc using commercial plugins

Hi @Kamal Iqlaas Ismail Please make an updateIssue after setting the value and see whether change is reflected. Refer to the function in https://docs.atlassian.com/software/jira/docs/api/8.0.1/index.html?com/atlassian/jira/issue/IssueManager.html

Do note that there is built in captcha lock feature available.. Refer to https://confluence.atlassian.com/adminjiraserver073/configuring-jira-application-options-861253962.html on the settings

Hello @Anita Chen These password settings are not available in the out of the box JIRA but if use Atlassian crowd for access management, it can offer * maximum number of invalid passwords attempts before the authenticating account will be disabled * number of days until the password must be changed * number of previous…

Hi @Juan Leon Welcome to community! Can you confirm that the field customfield_10003 is available in create screen of the project and issue type? Are you able to do the same operation from the UI successfully?

Hi @Janaki.R Sorry i missed adding another part to my answer. See https://library.adaptavist.com/entity/set-behaviour-multi-and-single-select-options-and-value about setting the options and then you can use the other answer about based on the other field to achieve your requirement. Hope it helps!

Hi @kdickason You can refer to https://library.adaptavist.com/entity/remove-specified-users-from-a-group and tweek it for removing the users from the group jira-users To get the inactive users, as mentioned in the page, you can refer to https://library.adaptavist.com/entity/deactivate-idle-users to get the list of users…

Hi @Janaki.R Checkout a similar question in https://community.atlassian.com/t5/Jira-questions/Auto-Populate-Multiselect-custom-field-values-based-on-single/qaq-p/1520358