Trudy P Claspill Community Champion

Hello @Adriana Cazacu Welcome to the Atlassian Community! Can you show us the mapping of Statuses to Columns for your board? Can you show us the Filter Query for your board? Can you show us an example of a newly created issue that is not appearing in your board?

Hello @Vicente Mondaca Welcome to the Atlassian community! It is possible that your email got blacklisted in the Atlassian emails servers. Your Jira Administrator can open a support case directly with Atlassian to find out if that is the case and Atlassian Support can whitelist your email address.…

Hello @Eric Younkin Do each of your tasks have only one inward and one outward linked issue? I think you don't need the .issue portion of the syntax before the .duedate portion. I have not actually tried to use the issuelinks property, but I did find this old post that that suggests alternative syntax.

Hello @Colin Davidson Welcome to the Atlassian community! Where are you expecting to see the Team dropdown? Are you expecting that to be a field in the issues? Do you see an option for Teams in the menu bar at the top of the screen (in the same area as pull downs for Projects, Filters, and Dashboards)? Do you see a Plans…

Hello @Colin Davidson Welcome to the community! Can you please share the query with us, and provide examples of items that are getting included that you think should not be included? It really is not possible for us to help debug the query without that information. You can change the values you show us to non-confidential…

Hello @Käthe Crautwickel Welcome to the Atlassian community! Are you working with Jira Cloud or Jira Server/Data Center? If your Jira URL is https://<something>.atlassian.net then you are working with Jira Cloud. If you are working with Jira Server or Jira Data Center, what version are you using? That information will show…

Hello @Toyosi Adebayo Manually triggered automation rules can be set up to be accessible to specified user groups as described here: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Manual Users selecting a manually triggered rule for an issue will see only the rules accessible to the groups to…

Thank you for that additional information. Are you working with issues in a Company Managed project or a Team Managed project? Are you able to manually set the Due date field through the UI? Can you add a Log action to write to the Audit Log the smart value you are trying to assign to the Due date field? Then try creating…

Hello @Jennifer Baum There is no feature natively available for limiting the values in the built-in Priority field based on the issue type. You could create your own custom field for Priority, and then create Contexts that set different values per issue type and project.

Hello @Kathleen Buckwalter What information is being written into the Audit Log for the rule when it executes? Notice below the rule name and "Rule Details" it says "Audit Log". Find the last entry where the rule ran and click on the Show More link to the right of that entry. Share with us the details.

Hello @Lisa Mills Welcome to the Atlassian community! What types of issues are these? Are they Epics with child issues? Are they Stories/Tasks with subtasks? The basic structure of the rule would be Trigger: field value changed: Event Date Condition: Issue Type = (the "parent" issue type for your scenario) Branch: (depends…

Hello @Josephine Maruta Welcome to the Atlassian community. You could open a request with Atlassian Support to ask them to provide the information. Alternately, in this post there is an answer suggesting some third party apps that might help.

You would need to: * Create a copy of the Workflow Scheme. The copy will automatically include the same workflows as the original scheme. * Add the new workflow to the copy of the scheme. * Assign the new scheme to the project you want to change.

Hello @Roshni Welcome to the Atlassian community! The feature to customize cards in a Team Managed project is not currently available. You can add your vote to the change request here: https://jira.atlassian.com/browse/JSWCLOUD-17336

Hello @Geo Mukkath Welcome to the Atlassian community! Have the users who don't see the division refreshed their browser tabs? Can you provide screen images that show the differences?

Hello @raju_bonagiri When you say you moved the Epic to "Component" do you mean you changed the issue type from "Epic" to "Component"? If so, did the issue remain in the same project or move to a different project? If it remained in the same project then the issue key (APPPPLT-2023) should not have changed. If you moved it…

Hello @Spencer Haven Welcome to the Atlassian community! The explanation is in the message displayed above the buttons. This workflow scheme is being shared by multiple projects. To edit this scheme, use the global Workflow Schemes page.

Hello @Neil Wills Only a person who is an Administrator for the board can switch the setting for Swimlanes. It can't be changed by an end user.

Hello @Lisa Hession Can you provide a screen image of your Project Board? Are you referring to a Kanban board? Do the Epics appear on the board when you don't have any quick filters activated? Have you set the Fix Version field for the Epics?

Hello @Helena Palys Welcome to the Atlassian community! It is not possible to dynamically change the columns displayed on the Kanban board to be only the ones relevant to a single issue type workflow when the board scope includes multiple issue type workflows. That is not a feature that is offered natively in Jira. All…

I know I've seen this same issue in another post, but I can't find the post. I believe in that post I recommended to the poster to contact Atlassian Support directly for assistance. They did, and got the issue resolved, but I don't remember the resolution. So, I recommend that you also contact Atlassian Support directly.…

Hello @Kodaganti Meghasri Welcome to the Atlassian community! If you are the Project Administrator for this project then you can create an Automation Rule to add yourself as a Watcher on issues. If you are not a Project Administrator for the project you won't be able to create that rule. What problem are you trying to…

Hello @Sebastian Braun Yes, this type of automation is possible. Have you tried to construct the automation? Please show us what you have so far. That basic structure would be: TRIGGER: Issue Transitioned ACTION: Create Issue ACTION: Comment on issue Use the smart value {{createdIssue}} to access the properties of the last…

Hello @tessa Welcome to the Atlassian community! Are you working with a Team Managed project or a Company Managed project? That information will show at the bottom of the navigation panel on the left. Are you working with a Scrum board or a Kanban board? If you are working with a Kanban board, and you always want the…

Hello @Minakshi Sharma Welcome to the Atlassian community. This page in the documentation for Advanced Roadmaps provides guidance on how to modify the issue hierarchy. https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/ Do note that changes you make to the…

Hello @Criselda Mora I believe your problem is in the code that you have used: "Story point estimate": {{issue.subtasks.Story Points.sum}} It needs to be: "Story point estimate": {{issue.subtasks.Story point estimate.sum}}

Hello @Dushyant Saluja When you create an issue manually in this project is the Issue Type field available on the Create Issue screen? The Issue Type field needs to be available on the Create Issue screen in order for you to see it in the Field Mapping screen when using the Import option as a non-admin user.

Hello @Federico Varchavsky You cannot use a Quick Filter to change the sort order of issues on an agile board. The sort order of the issues is built into the Filter Query used by the board. The only way to change the sort order is to change the filter query for the board. Note that if you set the sort order in the Filter…

It is possible to transition the issue in the other project, but it requires creating a Global Automation Rule, which can be done only by a Jira Administrator.

Hello @Charles Lindsay It is not unused. It is used internally by Jira to keep track of the issue's rank (position in Agile boards relative to other issues). It is not intended to be directly edited by people. People change the value by changing the position of the issue on an agile screen. More information about Ranking…