Comments
-
You need to check for an automation rule running at the time the issue was transitioned.
-
Hi Paul, You will need to open a support ticket with Atlassian to have them check to see if that email address is on a blocked list.
-
While on the issue, scroll down towards the bottom and click on the History tab. Or maybe just do a CTRL F on the ticket and search for History
-
Go to Settings > Issues > Workflows Then search for the workflow used by that project. Then click on Edit. Then click on the Transition (the line) that goes between the two statuses. Then click on Post Functions to see what is there.
-
Hi Anne, This is either built into your workflow - check the post functions there - or it's coming from Automation for Jira based on a rule. Check the history of the issue to see who is executing the transition.
-
Sounds about right.
-
Hi Mariana - Welcome to the Atlassian Community! I guess the best answer is it depends on how your team defines it. Each team might have a different interpretation of how that is implemented for them. Get together as a team and decide what it means for you. :-)
-
Go to Project Settings. Then Automation.
-
Ah, sorry! Forgot you were using Server. Good luck with the workaround!
-
Hi Soumyajit - Welcome to the Atlassian Community! No, you can only use forms with Jira Service Management and Jira Work Management/Business projects (simplified version of forms).
-
Ah, you are using a Team-managed project. You can create a global custom field with that type. Go to Settings > Issues > Custom fields Create the field with Date and Time. After you create it, edit the Context to add your Team-managed project. Then come back to your project settings and the Fields like above. Then click on…
-
Sure, go to Settings > Projects > Project Categories There you can create your categories. After those are done, then go to Project Settings for each project and add the category in the Project Details tab.
-
Hi Emma - Welcome to the Atlassian Community! I am confused about the form. There is no form available for Jira Software. Can you provide some more details about what you are trying to do?
-
Yeah, anytime you open up information for more people to see, it brings a lot more transparency. And a lot more questions!
-
Okay, still not sure that I am following, but you can create custom fields with date and time and then you can put the field on the Request Type form. Is that what you are trying to do?
-
Hi Mónica, No, there is no way to do that because when you create an issue it will always get created in the first status of the workflow. You can create a custom field with a dropdown of various values that the custom can select so your agent will know - but you can't use the actual status field.
-
Hi Dave, I know no way to doing this other than creating an email that is sent to users with lists of the issues with just the relevant information you want them to see. No need to put links on anything because they won't be able to see the issue even if they click on it.
-
Okay, that's beyond me then - sorry.
-
Which one is it? It doesn't fire? Or it fires with no update?
-
Hi Austin, Sure, just create an automation rule to send them an email. Start with a Scheduled trigger that runs once a day - whatever time of day you like, but maybe 5:00 am or so local time so it is sitting somewhat at the top of their In Box for email. Then add a JQL for the trigger - Project = ABC and statusCategory !=…
-
Hi @Satchidanand_CS_ext Check the Resolution field. If the field is empty, that's the system labeling it Unresolved. I would think you would want to change your wording for yours from Unresolved to Won't Fix, Won't Do, We don't know what the crap is going on with this, etc.
-
Sorry, no. I would open a support ticket with Atlassian to see if they do. Or they can add the feature request if they have not already. https://support.atlassian.com/contact/#/
-
Still not completely following this. Maybe just list exactly what you do and what you want to happen. Use identifiers such as Task A, Task B, Sub-task A-1, Sub-task A-2, etc.
-
Okay, thanks - check to see if you are in a project role such as Service Desk Customer project role or Service Desk Team role.
-
Sorry for the confusion - it wasn't clear to me how Epics were coming into the picture. Yes, it would probably fire for Epics also, so just add another condition at the top to see if the Issue Type = Story (or issue type not in (Epic, Sub-task).
-
That's probably it with the different field types. However, you might take a look at this previous post about Components - not the same field but would behave the same way I think. https://community.atlassian.com/t5/Jira-Software-questions/In-Jira-Automation-how-do-I-add-to-a-component-and-not-clear-the/qaq-p/2194124
-
Ah, that's probably the issue then. Maybe put in a Condition before editing the issue to check if the Fix Version is empty.
-
That would be for using an automation rule - not code. What exactly are you trying to do?
-
So you are sure the trigger does not fire at all? Or it fires and it just doesn't update like it should?
-
Create an automation rule based on an Issue Created trigger. Then add any conditions as needed. Then add an action for Edit Issue. Choose the fields you want to change. Place the text in the fields. If you want to keep what the user may have put in those fields and then add your text, use: {{issue.description}} and then…