Trudy P Claspill Community Champion

Oh, I see. I would suggest that you use the substringBefore function to pull the project key from the issue key. {{issue.key.substringBefore("-")}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#substringBefore-String-separator- 

Hello @Mimi Peters Yes, this is possible. You can use the match function against the Summary text field to pull out the number portion of the string. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#match-- If you use that to set the value on a variable you create, then you can use that…

Hello @Cash Coyne You could use the regex option described in the Answer on this post.

"Kana VR" is the project name. "STRES" is the project key. Changing the project name does not automatically change the project key because changing the project key can have other ramifications. But you can indeed change the project key through Project Settings. Note that when you change the Project Key that changes the key…

I think the problem is being caused because you are trying to set Labels in two different ways. You have specified JSON code for setting the Labels field, and you have also specified that you want to set it above that using the "Type to find value" option. You actually don't need the JSON text at all. You can use a smart…

What type of issue are you creating? It appears that you are using a Team Managed project. You can confirm that by looking at the bottom of the navigation panel on the left. And I see that you have the Backlog option enabled. For a Team Managed project, Subtasks and Epic issues are not displayed on the board. Subtasks also…

Another Community Leader (thanks @Esther Strom ) has confirmed that in their Jira Cloud environment it currently works as you expect; a user that has Assign Issue but not Edit Issues is able to change the Assignee field. They note that they have Release Tracks enabled for their system, so they may not have received all the…

Can you provide a screen image that shows what you are referring to when you say the "project title" and an image that shows where "2022" is still being used?

I see from the totals in the columns visible in the image that you have at least 999 issues on the board. Jira Work Management projects are limited in their Board view to 1000 issues. There is a change request about that here: https://jira.atlassian.com/browse/JWMCLOUD-23 Only the first 1000 issues entered in the project…

I'm glad I could help. If your questions have been adequately answered, please consider marking the answer as Accepted to help other users find posts with validated solutions.

Hello @Rodel Bernal Let me see if I understand your scenario. You have a Subtask Issue Type that is specifically for bugs discovered related to an issue. When you discover a bug related to an issue you create an issue of type Subtask Bug and this is a child subtask under the issue. And then you might change the parent of…

The problem with Automation 1 is that you are triggering it based on a change to the Sprint field. So, yes, when you add an issue to a future sprint the Sprint field will be updated and the rule will run. That is the trickier situation for which I have not had time to work out the steps. I think it might work if you add a…

Hello @Tiziana Garigali Welcome to the Atlassian community. Basic Users can create spaces and administer them if you give them that permission. You would do that from the Global Permissions page: https://<your URL>/wiki/admin/permissions/global

Is the field available on the Edit screen for all the issues that are within the scope of the selection you made for Bulk Change?

Hello @mbitzis Welcome to the community. Are you working with Jira DC or Jira Cloud? You mentioned Jira DC in your post, but your post tags indication you are using a Jira Cloud Free subscription. In Jira Cloud it is not possible to mention User Groups, but it is possible to mention Teams.

Hello @Linda Korpås It is possible to synchronize the statuses with the "normal" Automation Rules feature. Because you will be looking for changes to issues in the software project and wanting to update issues in the service project the rule will need to be a Global rule. The Scope of Projects for the rule will need to be…

Hello @Rosana Casilli What are the details of the Trigger step? What is the field customfield_10458? What type of field is it? What data does it contain? What is recorded in the Audit Log for this rule when it executes?

Hello @Fahad Akhtar Can you explain the problem you are trying to solve by having multiples copies of these issues in different projects? Perhaps we can suggest an alternative solution that doesn't involve copying the issues.

Note this solution suggests moving issues from one project to another. The OP wants to copy all details of all issues into multiple projects.

Here is a change request related to that: https://jira.atlassian.com/browse/JRACLOUD-77492

It would be great if you can report back here what your admins learn from Atlassian support.

I encourage you to open a support case directly with Atlassian, and include the links to the posts I added above to show that other users are reporting the same problem. https://support.atlassian.com/contact/#/

Hello @Matt Ohlson (Vendor) Welcome to the Atlassian community. You appear to be missing a closing curly brace on Assignee. { "fields": { "assignee": { "id": "{{89.owner_email}}"}, "duedate": "{{3.`DE:Launch Date`}}", "project": {"id": "14505"}, Additionally have you confirmed that 14505 is a valid ID for a project?

Hello @Steve Hooczko Add a Field Required Validator to the workflow transition.

Adding to this... The Resolved date gets set when the Resolution field gets set. The Resolution field is separate from the Status field where you set the status of the issue to Done (or Closed or some other done/green status). And the Resolution is not necessarily automatically being set when an issue transitions to a…

Hello @Anna Dora Winius Welcome to the Atlassian community. Are you working with a Company Managed project or a Team Managed project? That information will show at the bottom of the navigation pane on the left. The Epic Panel in the Backlog screen is displaying issues based on the status of the Epic. For a Team Managed…

I think this will work project in ("<MyProject>") AND status in (Closed, Done, Built) AND "Story Points" > 0 AND labels = label1 AND labels = label2 AND issuetype not in sutaskIssueTypes() AND ( timespent > 0 OR ( issueFunction in subtasksOf("project in ("<MyProject>") AND status in (Closed, Done, Built) AND "Story Points"…

I have found two other posts that mention this same problem. https://community.atlassian.com/t5/Jira-Software-questions/Assignee-can-t-be-edited-in-edit-mode/qaq-p/2355784 https://community.atlassian.com/t5/Jira-Work-Management-Questions/User-with-permissions-still-cannot-assign-issue/qaq-p/2355067

Hello @Maegan Burleigh A variable that is created within a branch will not be accessible outside of that branch. You need to add a Create Variable action with the same variable name before the For Linked Issues step. Keep the same action in the For branch to reset the value of the variable.

Hello @jimconn Q1 - The message you are receiving indicates that there are Subtask type issues already created in your project, and you are trying to associate an Issue Type Scheme that does not include a Subtask issue type. A project can have only one Issue Type Scheme associated to it at a time. That one scheme must…