Trudy P Claspill Community Champion

Hello @Dave Hattig There does not appear to be an option for setting the text color of the menus. When you select a menu background color that is "dark" the text color is automatically changed to white, and that affects the text color in the pull down. But the selected menu background color doesn't appear to apply to the…

Refer to the documentation for the Edit Issue endpoint here: https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-put

Any change to an issue will update the Updated date/time field. To find issues that have had no change whatsoever in the past X days you could use: updated <= startOfDay(-Xd) There is not a native function to let you filter based on the date of the last Comment. You might be able to find that capability in a third party…

If you wanted to constrain the Project B Epics included in the board to only those that are parents of issues in Project A, that would take a more complex filter. In this case what you would want, effectively, is project="Project A" or (project="Project B" and issue in ParentEpicsOf("project='Project A'")) ("ParentEpicsOf"…

You cannot change an issue to a Status that is not part of its workflow. An issue can have only one workflow applied to it. You can combine issues that have different workflows in one board, which is what you have done, but the issues still can follow only their own workflow.

You can put whatever you want in the Subject and Content fields. Those will be the Subject and Content of the email that is sent. What information do you want to include?

Hello Jeff, The current rule you showed doesn't show any steps for summing child story points to the parent Epic. Do you have another rule that does that? Or does the image not show the entire rule? If you want to do a one-time sum up of child Story points to parent Epics that are already in progress, you could do that…

Hello @Greg Encke Welcome to the Atlassian community. An alternative to the suggestion from @Gustav Lindskog is to create Quick Filters that select issues based on JQL; i.e. parent=<Epic issue key of an Epic in the other project> You would need to create a Quick Filter for each of the Epics in the other project with each…

Hello @rneill19 When you say you are creating an issue from an Epic, do you mean you are adding a child issue? And from the Epic it is just adding a line under Child Issues for you to enter the Summary? It should automatically open a dialog for entering data in other issue fields when either a field has been set as…

Hello @Maxie Brown Welcome to the Atlassian community. Is "region selection" a custom field in your issues? Assuming it is, you will not be able to modify the Notification Scheme for the project to meet your requirement. You could implement your requirement with Automation Rules.…

Adding to this... If the projects that you now want to move shared configuration items (fields, schemes - screens, issue types, permissions, notifications, workflows, etc.) with the projects that have already moved, and if any of those items have been changed in Cloud, then using JCMA to migrate the remaining projects can…

What is the current Status of the issue you are trying to drag to the QA column? What is the Status that you want to change it to? Is that status available in the workflow for the issue you are trying to move? Can you share with us the Column/Status mapping information for this board? Is that new status mapped to the "QA"…

Hello @Jeff Murray The rule you wrote is intended to change Epics that are not "in progress" to "in progress" when one of their child issues changes from "to do" to "in progress. As written that rule will make no change to an Epic that is already "in progress". There is not need to make a change in that case. From your…

No, not all System Fields will be displayed on cards on the board. For a Team Managed project there are a few fields that display automatically on the cards: Issue Key Assignee Priority Summary Due date Labels Parent Epic the symbol for Subtasks, if there are subtasks under the issue There is not a comprehensive list of…

Hello @Jeff Murray How do you want to update the Epics that are already "in progress"? Do you want your first rule to work for Epics that are "in progress"? If so, please show us the details of that rule so that we can determine why it would not be working for "in progress" Epics.

Hello @mathieu.tanre Welcome to the Atlassian community. The tags on your post indicate you are using a Free subscription. If that is true, it isn't possible to modify the permission for your projects. Refer to the first paragraph of this document:…

Hello @soju chacko Welcome to the Atlassian community. Another alternative is to ask your administrators to create a Team Managed project for you and specify you as the Project Administrator. Project Administrators can customize the Workflows, Fields, Issue Types, and more specifically in their Team Managed projects.

Hello @Sjoquist, Carl Click on the Plans menu and select Settings. Select Dependencies. Use this page to add back to your Plans the Link Types you have recreated and want to use in the Plans.

That's great, Carol! If our responses have helped you solve your requirement, please consider clicking on the Accept Answer button above the response thread(s). That will mark you Question as Solved, and help others searching the community find the posts with validated solutions.

You can't create a new field while the rule is running. You have to create the new field separately and add it to the project/screens for the issue types where you want to use that field. You can copy the information from the input field in the trigger to a field in the issue by using the Smart Value for the input field.…

Hello Youmna, Are you trying to drag the card to a different swimlane at the same time that you move it to another column? That would not be allowed. A swimlane is a horizontal grouping of issues based on a common value (blue box). You should be able to move issues to another column in the same swimlane (green arrow). But…

Hello @LOUIS MICHAUX Labels will not interfere with the display of the Due date. Can you show an example of an ITOP issue where the Due date field is filled in, and the corresponding display of the card on the board? Are you using the "Due date" field that is built-in to the project or did you create a new custom due date…

Hello @Theresa Gerhäuser Generally Epics should not be added to sprints. Sprints should contain only the issues that you are committing to completing within the sprint. Epics typically take longer than the duration of a sprint to complete. What problem are you trying to solve by adding Epics to Sprints? Given that this…

Hello @Arturs Kalnins The "Reopen Reason" field exists only on the screen that displays when you trigger the rule. It is not a new custom field that has been added to the issue configuration. If you want to store that information in the issue, then need to copy that information into an existing field in the issue as part…

In the results you got from extracting all the fields, can you check if there is more than one field named "assignee"?

Hello @ribas That is not possible with the native functionality of Jira Data Center. Are you willing to consider acquiring a third party plugin to achieve your requirement?

Hello @LOUIS MICHAUX Welcome to the Atlassian community. Please tell us the project type for the project that contains the issues, for both the ITOP and ADC projects. You can get that information from the Type column on the View all projects page under the Projects menu. For a Company Managed Software project, it is…

Does the Assignee field for that specific issue actually have a person specified in it?

The general structure provided by @Tugba Capaci is correct, except for the Condition suggested. You can use an Issue Fields Condition (1) to compare the value of one field to another field of the same field type. Pick Reporter for one field (2). By default the second part of the comparison will the set to Value. Click…

Hello @Tugba Capaci "key" is not a documented attribute of a user field, as per https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/ Did you test this and find that it actually works?