Trudy P Claspill Community Champion

Hello @Suporte scadaHUB Welcome to the Atlassian community. How exactly have you determined that you have "maximum permissions"? Are you an Organization Admin for the Organization under which the site exists? Are you a Jira Software Administrator? Are you a Jira Service Management Agent for this project? Do you have the…

When you have a question about an app that you have added to Jira you should first review the documentation for the app. You can find the link to the documentation on the Support tab of the Atlassian Marketplace listing for the app.…

Hello @Yaron Norani Custom fields created within a Team Managed project are unique to that project. Creating a custom field in another TMP project with the same name is creating a new, separate custom field. When you Moved the issue you should've seen a screen something like this: On this screen did you map your source…

Hello @Don Hames That role is used exclusively for apps that are added to your instance, such as the apps available in the Atlassian Marketplace. It is not a role that you would grant to an actual person. Some apps require specific permissions to projects to provide the functionality they advertise. That role is used to…

I have never seen {{link.issue}} used in an Automation Rule before, and I'm not finding it in the documentation. Where did you get the idea for using that smart value? I suspect it is not a valid smart value.

Hello @Anoop VK Welcome to the Atlassian community. There is not a page in the UI that lists the System Fields. There is a page that lists Custom Fields which includes fields you have added and some fields that are added automatically by Jira Software and/or Jira Service Management. When you say you want to add a value to…

Hello @John Kissel Welcome to the Atlassian community. To which plug-in are you referring? This community is for the Jira application. Jira is not a plug-in but rather a full-fledged web application. Can you explain what problem you are trying to solve?

Each time a rule executes an entry is added to the Audit Log for the rule. You can expand an entry to see details about the execution of the rule. The details will tell you the issue that triggered the rule, if conditions did or did not match, and if detectable errors occurred. Can you show us the details from the Audit…

@Kevin Dickson Welcome to the Atlassian community. The Swimlanes by "Epic" option is based on the Epic Issue Type. If you rename your Epic Issue Type as "Feature" then the Swimlanes by Epic becomes Swimlanes by "Feature", remaining tied to the issue type that was originally "Epic" The only way to base swimlanes on custom…

Hello @Ana Vitória de Paula Rothebarth Welcome to the Atlassian community. Can you please provide screen images of the rule you created, and the details of each step?

First, in the JQL for your Lookup Issue action remove the "<" and ">" characters surrounding your Project Key. I used those characters to indicate a variable you needed to replace. You want only the actual project key there, not those extra characters. Regarding setting the Assignee, you don't want to use "User who…

Hello Anja, Is this for a Company Managed project or a Team Managed project? If for a Company Managed project another alternative would be to create another Board and there have the Backlog status not mapped to a column. That would prevent all issues in that status from being displayed, but would enable the PM to have a…

If your question has been satisfactorily addressed, please consider marking the Answer as Accepted to help other users find posts with useful answers.

Yes, the behavior of the boards for different types of projects (Software vs. Work Management, Company Managed vs. Team Managed) is a bit different.

Hello @eldiep Welcome to the Atlassian community. First, are you working with a project that is Team Managed or Company Managed? That information will be shown on the View All Projects screen and at the bottom of the panel on the left when you view the project. Next, is it a Software project or a Business/Work Management…

Hello @Khaoula ATALLAH Welcome to the Atlassian community. If you add a new issue type above the Epic level in the Issue Type Hierarchy, you are telling Jira that you want that new issue type to be a Parent to the Epic issues. If you want to add a new issue type that can be a Child of an Epic, like Stories and Tasks, then…

Hello @charlotte StatusCategory allows you to query for issues based on the Status Category to which the issue's current status belongs. StatusCategoryChanged records only the last time a status change resulted in a change of the Status Category of an issue. These fields don't give you a history of Status Category changes.…

Hello @malli_tech1994 No, you will have to purchase a new license in order to perform an upgrade.

Hello @Владимир М. Welcome to the Atlassian community. If you exceeded the 10 user limit for the free version you site would've been automatically upgraded to a Standard subscription. Your Technical and Billing Contacts for the product subscription should've been contacted by email when that occurred. If your site…

Hello again @Elif Alverson The locked Category field is used by the Business/Work Management projects. The values that are available are specific to the project and created/managed within the project. When you say the field is used by multiple projects are you referring to Business/Work Management projects or are you…

Hello @joecline Since it is a Company Managed project you need to review the Permission Scheme associated with the project and check who has been granted the Browse Projects permission in that scheme. That is the permission that determines if a user can see your project. If you don't readily see the problem when you do…

I'm going to jump in to see if a different voice can shed some light. If you are familiar with a Company Managed project Kanban board, you may be familiar with the concept of mapping statuses to the Kanban Backlog. When you map a status to that area, that enables the Backlog screen for that kanban board. The issues that…

Hello @Emmanuel Lehmann Based on what you say you can see, you are interacting with a Team Managed project. Kristopher's answer only applies to a Company Managed project. (You can see which type of project it is by looking at the bottom of the panel on the left, where the text will include either "team-managed" or…

Hello Patrik, I inferred from the author's post that they wanted time logged each time the issue was transitioned to another status, to capture the time spent along the way, as can be done with a Transition Screen in a Workflow for a Company Managed project. Your solution only ensures that the total Time Spent on the issue…

John didn't say that he contacted support. He recommended that you contact support. Atlassian support is going to want to access your system to see if they can replicate the issue. John can't give them permission to do that. Only your Jira Administrators can do that.

Hello @Robert Ban There are triggers for Automation Rules for Field Value Changed and for Issue Updated. You would use one of those to detect that the subtask was changed. You would then add the following steps: Condition: to check that the changed issue is a subtask Branch: For Related Issues / Parent Action: Edit issue -…

Hello @Martina Bassi Welcome to the Atlassian community. when a case is re-opened, we would like to mark it as re-opened and we would like to see this information next to status field. Something similar to Resolution field. No, it is not possible for you to place a field next to the Status field, in the same area where you…

This rule would allow the issue to transition if any time was logged at any point prior to the transition. This rule would not force the user to log additional time as part of completing the status transition. In a Team Managed project there is no method to require a user to enter data while making an issue transition…

Hello @[deleted] Welcome to the Atlassian community. Your post is not self explanatory. Please provide more information. 

Hello @Anja Eigner I assume that in your scenario "Backlog" is an issue Status. The design of the Scrum boards in Jira is such that an issue can be in any Status while assigned to a Sprint. The issue will show in that Sprint regardless of the issue's Status. You can't remove the "Backlog" Status/Column from the Active…