Trudy P Claspill Community Champion

Are you able to edit Story issues that are not assigned to you? It sounds like the permission scheme for the project has been set to limit who can edit an issue, with one of the allowed editors being the current Assignee.

Are you using the Jira Software product, the Jira Work Management product, or the Jira Service Management product? Are the 3 projects Software projects, Work Management projects, or Service Management project? A Work Management project will have navigation option arranged horizontally across the top of the screen, such as…

The Epic Name field is an attribute used only in the Epic issue type. The name of the parent Epic is not stored in the Epic's child issues. Only the parent Epic key is stored in the child, and that is in the Epic Link field. The UI automatically transforms that field to display the related Epic Name when your are view the…

Hello @Swati Rastogi This is the rule you'll need. The smart value in the Create Variable action is: {{fieldChange.from.toDate.diff(fieldChange.to.toDate).days}} The smart value in the Edit action is: {{issue.duedate.plusDays(dueDateDiff.asNumber)}} You may want to change the Condition where I'm checking that the trigger…

First, it is a bad practice to have multiple custom fields with identical names. This can lead to unexpected behavior and "confusion" when trying to use the fields by name because Jira is may be unsure which field you actually want to use. I strongly encourage you to consider changing the name of the Category (checkboxes)…

Hello @Adrian Constantinescu I think there is some confusion over terminology. "repo" is not a term that applies to the Jira product. "project1.atlassian.net" is the site where you Jira product is installed. A Jira product can contain multiple projects, each containing issues. To change the URL of a site you would follow…

Hello @Cirilo Alex Cavalli Can you tell us the steps you are going through to create your filter, and show us screen images where you expect to find the filter but it is not appearing?

That confirms that the Lookup is finding issues, and the first one in the results set does have a valid priority value. Can you show us the details of the Edit step again, since you changed it? I want to confirm that is contains the following without any typographical errors. {{lookupIssues.first.priority}} When you were…

Is this using the built-in Category field or another custom field you created and named Category? I ask because I have only the built-in Category field, and I am not able to select that field in the Edit action. I tried in both a Company Managed and Team Managed Work Management project. So I wonder how you were able to do…

Based on the screen image you provided you are viewing the Default Field Configuration. You can confirm that at the top of the screen. When you set a field as Required in the field configuration, then that field becomes required for all issue types to which that Field Configuration has been associated through a Field…

Based on the screen image posted in @Robert Wen_Cprime_ 's Answer thread, my answer doesn't apply to this situation.

Are you working with issues in a Team Managed project or a Company Managed project? That information will display at the bottom of the panel on the left when you are viewing the project or you can find it in the Type column on the View all projects page. I tested the rule I provided against both types and it worked. Please…

Then you should be able to construct this query in Enhanced Search to get the Epics of the issues in the ODF project where the Epics exist in the ART project. issueFunction in epicsOf("project=ODF") and project=ART Save that filter. Then construct a second filter to retrieve the child issues of the Epics from the first…

Bonjour, Vous utiliseriez l'option de branche pour l'étape 3. Après avoir choisi le type de branche (problèmes liés), vous sélectionnerez ensuite Problèmes liés comme type de problèmes liés. Vous devrez également spécifier le type de lien que vous utilisez entre les problèmes. --- Hello, You would use the branch option for…

Click the Search field in the menu bar near your avatar. In the resulting pop-up at the bottom is a Go to all option with a Boards button. Click that button to get to the screen that lists all boards and includes the Create Board button.

Where you have used the smart value to set the priority field, the "i" in "lookupIssues" needs to be capitalized.

Hello @mfrench Welcome to the Atlassian community. Please show us how you set up the Behavior.

Hello @ks_hyeon Review the settings for the project and the JSM product to confirm that self-signup is actually still enabled. Refer to the section "Set up an open portal" in this document: https://support.atlassian.com/jira-service-management-cloud/docs/set-up-and-manage-portal-access/

Is the subscription for the destination site/product Premium or Enterprise? If so, then AR is automatically available. If the destination site is using a Standard subscription, then the issue hierarchy can't be extended with native functionality. There may be an Initiative issue type in the destination site, but without AR…

Have you considered setting up a separate site under your Organization where you would install the JWM product? That would allow you to segregate between the two sites/products the third party apps you want to use for each.

Hello @Elif Alverson I believe you need to choose Copy From Epic rather than Copy from Parent to copy the value from the Epic to the Child Issues found by the For: Stories branch. You could set up a second rule to be triggered on the change of Category for the Stories, and add a similar branch to update the subtasks of the…

Hello @Robb F Watkins Native JQL functionality is not capable of getting you the results you want. It would need to do something like this: Filter 1: The stories from ODP that have a parent Epic in ART Filter 2: All the children of Epics identified by Filter 1 example: issue in childrenOf( parentEpicsOf(project=ODF) and…

Hello @Greg Davis Looking at the board image you provided that appears to be for a Team Managed project. Is that correct? You can confirm that by looking at the text at the bottom of the panel on the left when you are viewing your board. That text will include either "team-managed" or "company-managed". A board is…

Does it happen consistently no matter what Epic you try to add to a specific story, or does it happen only for certain Epics regardless of the the Story to which you try to add them? If it happens for certain Epics regardless of the story to which you try to add them, then are all the Epics in the same status, and is that…

Hello @Diatta Harris Another possible explanation is that the Create transition in the Workflow has a Validator to ensure the Reproduction Steps field has a value, and both issue types use the same workflow. In that case you would need to make a copy of the workflow, remove the Validator, and then update the Workflow…

Hello @David Holman Is this a self-hosted to self-hosted, self-hosted to Cloud migration, or Cloud to Cloud? I don't know it for a fact, but my theory is that if the destination environment doesn't have AR then while the issue type might be retained the structure cannot be retained. Without AR there is no way to visualize…

Hello @Hollee I see you created your own Question for this. I posted a response there: https://community.atlassian.com/t5/Jira-Software-questions/How-can-you-inherit-fields-from-two-independent-Jira-boards/qaq-p/2440219 

Hello @Hollee To consider issues in multiple projects within your rule the rule must be multi-project. Only a Jira Administrator can create a multi-project rule, and that can be done only from the Global Automations page available to Jira Admins in Jira Settings > System.

Yes, you would use the SET option and type in the smart value. Please show the details of your automation rule and the details of the Edit Issue step. Could you also paste as text the message in the log, so that I can run it through a translation app?

You would have to look at leveraging the Automation Rules functionality to detect new comment creation and manipulate fields that will display by default in the card, such as the Labels and Flag option. The trick then becomes figuring out how to remove the Label or Flag that was used to indicate a new comment was created.…