Trudy P Claspill Community Champion

If you are getting that message when trying to create a Company Managed project then you do not have the Administer Jira global permission. The person who created the site and the Atlassian Cloud Organization under which it exists would have the highest level permissions. There are other administrator roles that may be…

Deleting a custom field in Jira Cloud is a two step process. First you move it to the Trash bin. Then you can proactively force the deletion, or you can wait for it to be automatically fully deleted after 60 days.…

Company Managed projects can be created only by the people with the Administer Jira global permission, similar to the Jira DC environment. By default a new Jira instance is configured to allow anybody to create a Team Managed project. That is another Global Permission. When Jira Admins create new projects following the…

Ah, yes, now I remember. The self-reflecting transitions are not listed under the Status pull down. They are listed under the Actions button.

@Neeta Dubey To get help with your automation rule please provide screen images that show your entire automation rule and the details of each step. Also, what is the default unit of time that is used when you enter time with no qualifier? If you enter simply 10, does that save as 10 minutes or 10 hours or 10 days? Estimate…

@PLaksh11 Yes, you can get what you want with ScriptRunner using the linkedIssuesOf() function. https://docs.adaptavist.com/sr4jc/latest/features/scriptrunner-enhanced-search/jql-functions#linkedissuesof project = "Newhw" AND type = "Root cause" and issueFunction in linkedIssuesOf("project='Newhw' and issuetype='Bug' and…

@Prem No your modified query also does not work. The criteria issuetype="Root Cause" ...tells Jira you want only issues of type "Root Cause" in the results. The criteria and issuetype != "Non Software" is not applied to the linked issues, which is what @PLaksh11 is asking for.

Ah, yes, the rule execution limits. With a trial the limit is quite low. So, again another good tactic is to use the Log action to print out all the field values and calculations that you would use in your rule before adding any actions to change issues. A rule that has only Log actions does not count against your monthly…

Hello @Prem Your answer is not correct. @PLaksh11 asked to get a list of only the Root Cause issues that are linked to only Bug issues. Your JQL will provide Root Cause issues linked to any type of issue with the "causes" link.

Is this a Software, Business, or Service Management project? Can you show us the diagram for the workflow? What do you see when you click on View Workflow at the bottom of the Status pull down in the first image you posted? I would like to see from your workflow the comparable output that I have boxed in red below. Does…

Hello @PLaksh11 That is not possible if you have only native Jira JQL functionality available to you. It is possible with third party apps. Are you willing to consider getting an app that extends the capabilities of JQL? 

Are you working with a Team Managed project or a Company Managed project? If it is a Company Managed project, did you Publish the new workflow? Did you refresh the issue screen after publishing the new workflow? Did you change the workflow that applies to the issue type you are viewing? Can you show us the Workflow…

Hello @Barry Neilson A black circle with an "i" next to the rule name usually means you have put something into the Rule Details Description field, and if you hover over the "i" it will show you that information. Can you provide screen images of the rules and the Audit Log information? Sometimes there are typos in the…

Hello @[deleted] Yes, it is possible. You have to create a special transition from that state to the same state. This is referred to as a Looping or Self-reflecting transition. That is mentioned in the following reference: https://support.atlassian.com/jira-cloud-administration/docs/work-with-issue-workflows/…

Hello @Noman khan Welcome to the Atlassian community. Do you fill in the Organization field for each request? If so, you may be able to include that information in the email using the variable ${issue.Organizations.name} I have not tested that. I am extrapolating from documentation I've found that it might work. A user…

Hello @Julianne Cowan-Johnson Welcome to the Atlassian community. Based on the unresolved status of the following suggestions I don't think that is possible: https://jira.atlassian.com/browse/JWMCLOUD-98 https://jira.atlassian.com/browse/JWMCLOUD-136

Hello @neha jagwani Exactly how did your manager assign you admin access? And exactly what admin access did they grant you? There are different types of admin roles that have different abilities. The types of admin roles available in your environment may depend on whether you have the new or original Billing experience,…

They don't appear to be interested in providing that functionality. You might consider contacting Atlassian Support about having a change request opened and/or providing that feedback to Atlassian through the Feedback option under the Help menu within Jira 

A support case should be opened on your behalf and an Atlassian team member should reply in this thread within 2 days.

It does not seem to me to be a documentation failure. It states the limitations directly below the title of the page, in a purple box.

Hello @Barry Neilson Your post tags indicate you are working with a Free subscription. Are you working with a trial of a Premium subscription? As noted at the top of the referenced document, the functionality is available only to Premium and Enterprise subscriptions. You must first have a Plan (a.k.a. Advanced Roadmaps in…

Have you confirmed that the Watcher custom field is actually accessible in your second project? Have you checked with your Jira Administrators to see if they already have the Automation set up and can apply it to your project?

When you sign up for the free product and create a new site, the Organization is automatically create and named the same as your site (road-project), and it would make you the Organization Admin. Have you ever seen the Administration option in the Navigator? Had you ever previously accessed the parent Organization for the…

Hello @Nate Dickinson The deactivation/removal of Customer accounts is not something that JSM Cloud does automatically. You should start by consulting with your Jira Administrators to find out if they have put some process in place to identify inactive customers and remove them.

There is not a native field available to see the Watchers names other than looking at the individual issues. Notice in your fist project that the number in the Watchers column doesn't match what is shown in the Watcher column. That indicates that those two fields are not being kept synchronized. To see the names from the…

Hello @Mina Markovic Welcome to the Atlassian community. Can you clarify how your question relates to the Jira product from Atlassian?

The Watchers field is the count of people "watching" the issue. This will match the information that appears here: Watcher (notice that is singular with no "s" at the end) is not a native field of Jira. That appears to be a custom user picker field that has been added to your environment by your Jira Administrators. There…

Hello @Steve Hooczko We are going to need more information. What type of project are you using? Get that information from the Type column on the View All Projects page under the Projects menu. You can't use project Permissions to set visibility for subsets of issues in the project. Project Permissions apply to the entire…

Hello @Cadena_ Hector Welcome to the Atlassian community. Can you provide a screen image to show an issue where the watcher column is filled in correctly and one where it is not? In the project where this is not working, what information do you expect to be added to the watcher column? Is it adding only partial data, or…

Hello @Gino Marckx Welcome to the Atlassian community. The only way the product can be removed from your profile is for the Administrators of that product to revoke your access to it. It is not possible for an end user to "leave" a product on their own. Atlassian Support will not revoke your access to the product. They…