Comments
-
Hi Iveta, Start by looking at the Issue Type Scheme associated with the project. Go to Project Settings > Issue Types Make sure that the issue type is there. If not, then add it. If there, then check the Workflow Scheme to see if that Issue type is mapped to one of the workflows in the scheme. If not, then add it.
-
Go to Project Settings then Issue Types Then you need to edit the Issue Type Scheme to add the statuses. If they don't existing in the default list, you can add them at that point. You will need to be a Jira System Administrator to be able to do that.
-
Hi Suleyman - Welcome to the Atlassian Community! Check the Permission Scheme for the project and make sure that the Assignable User permissions apply for the user you are trying to assign on this project. (If you want a User automatically assigned). Otherwise, remove the setting where the user is automatically assigned…
-
Hi Roi, Not that it should make any difference, but I would edit the Rule Details to only run the rule on the CMS 2020 Test project. Then you can remove the If: Project equals step. That should help with the count against your executions. Does that Sprint span multiple projects?
-
Hi Amit, Do you have a filter built already? Can you share that? Is it giving you the list expect? If so, then add a column to the filter results for LinkedIssue - it will show up as Links in the column heading.
-
Hi Amz - Welcome to the Atlassian Community! So you are trying to create an issue on a project and you don't see those types?
-
Hi Eoin - Welcome to the Atlassian Community! The fastest way would be to edit your filter to remove two of the projects at a time and then go back into the bulk edit to see which one gives you the problem. It's most likely linked to the Permission Scheme for the project that is giving you the problem. Either you don't…
-
Actually you might just try the add-ons user. That should also accomplish it and not have to specifically use the Automation user name.
-
Great! Glad I could help a little.
-
Hi Samuel, You might also try the Hide transition from user condition. It should still execute with Automation For Jira but be sure to test it out.
-
Go to Board settings > General There you can see the filter that is attached to the board and change it or connect to a new one
-
Yes, you need to add more statuses. :-) You add the statuses in the workflow itself. So you will need to edit the workflow. Since it is simplified, you should be able to get by going to Project Settings > Workflow
-
You would not see a note in the history of the issue for when an email is sent. Does the email text saying anything related at all? I think you might have to start with all of the rules you have and go through one by one to see which one might be doing it. But it has to be coming from somewhere. On a side note - what type…
-
Hi Jeannette - Welcome to the Atlassian Community! There should be some changes to Next-gen projects for Done issues coming soon. You can follow along in their roadmap here: https://www.atlassian.com/software/jira/whats-new/next-gen?_ga=2.104316484.513035551.1586779195-1313086432.1576012938#intheworks
-
If I understand correctly, the rule is fired when a sub-task is created. Correct? But there is no component in your rule that sends an email. Correct? But the email is coming from Automation For Jira. Correct? So that tells me that there is another rule somewhere that you have that sends the email - outside of this rule.…
-
Statuses are a part of the workflow linked to the project. Then the statuses show up on the right in the Unmapped statuses section. Since there are no statuses there you need to check what workflow is attached to the project used by the board. There's no button to press to start the process.
-
The warning would be in the email sent to them 10 days in advance. Also, what's the harm of them ticket sitting idle in the Backlog for 50 days if it automates your process and works?
-
Hi Rich - Welcome to the Atlassian Community! Who does the email say it is coming from? Do you have a step in your rule that sends and email? Have you checked the Notification Scheme for the project to see when emails are sent?
-
Hola Yeniset: ¡Bienvenido a la comunidad de Atlassian! Supongo que mi pregunta sería, ¿por qué tendrías más de 1,000 problemas en una sola placa? Eso es inmanejable en mi opinión. Seguramente puede dividir eso en otras placas por equipo o por función o por componente o algo.
-
Hi Elaine - Welcome to the Atlassian Community! You need to have a status mapped to the column in order for the column to show up when you view the board.
-
Great! Glad I could help!
-
Hi Mathew, This is what I use for a field change: {{issue.key}}'s {{fieldChange.field}} field was updated from {{fieldChange.fromString}} to {{fieldChange.toString}} by {{initiator.displayName}}. It fires when the field is updated so I assume it will work for fixVersions also.
-
Hi Jay, If the user does not have access to the issue via the issue level security, then sharing it will still not give the user access. The user must meet the criteria of the security level period - no matter how he/she gets the link to the issue.
-
See my example above for syntax. To start, click in the Search box Then click on Advanced search for issues. Then put in the search.
-
This appears to be by design. You can add the field as a hidden field to the portal and populate it with a value. But it's not one you can let users select. See this closed request: https://jira.atlassian.com/browse/JSDCLOUD-2084
-
Hi Akhil and Welcome! We are glad you are here!!
-
Thanks for the explanation. Try adding a Branch rule (the purple one) and select Issues in the sprint for the second component (right after When Sprint started). The put all of your conditions under that and see if it helps you.
-
Hi @simarpreet singh , The Epic Name is actually attached to the Epic and is not a field linked to other issues. Have you tried to show the Epic Link on the JSD Portal?
-
Hi @Be Victoryus - Welcome to the Atlassian Community! If you completely delete a project, it should let you reuse both the name and the key. I would give it a try again, and if you still get the same error, can you post a screenshot here?
-
Great! Glad it is working for you! Can you share your rule so I can understand the type part better?