Comments
-
Again, I would create a Project Category for those projects and add it to the PMO template (PMT) project. You could call the category PMT or PMO if you wanted. Then all projects created with that template would inherit the Project Category. Then you can use a smart value condition for a Project Created trigger to see if…
-
Hi Emiliano, Try: {{triggerIssue.key}} - Meetings
-
Hi Jack, What exactly are you wanting to add? We need more specifics please.
-
Hi Phil, Take a look at this document to help guide you. https://support.atlassian.com/jira-service-management-cloud/docs/add-a-customer-to-an-organization/
-
You are welcome.
-
So you are just doing an update and not a create? It's probably that there is not a valid transition between the current status and the new one. I would modify the workflow to add an ALL transition to every status. Then add a Condition so that only the person doing the import is able to execute the transitions. That way no…
-
Hi Shashank, I suggest you contact the vendor directly.
-
Hi Luke, What's the relationship between the issues? Are they both Epics? If not, what issue type is the issue in Project B?
-
HI Kiran - Welcome to the Atlassian Community! Are you using the built-in Teams field in Jira? You said you have a custom field - what type of field exactly is it? Group picker? Multi-user picker?
-
Hi Fatima - Welcome to the Atlassian Community! There currently is no smart value for workflow schemes. What is it exactly that you are trying to do? You could probably accomplish what you want with the Project Category.
-
Hi Mohammed, You can create a separate screen scheme with separate screens for the parents and children. Then simply at the field the the parent screens, but not the child screens.
-
Hi Yehonatan - Welcome to the Atlassian Community! If you are talking about the key (or ID) of the issues, that is not possible and you have no control over how those are populated. The key of the issue will be the project - sequential number. You have cannot change that.
-
Hi Amar, If you are using a Company-managed project you can create both types of boards in your project and connect them to different issue types using the board filter.
-
Hi Javanshir, Can you share the rule that you have so far please? Also, if you use If/else, the rule will stop when you meet the condition the first time. That’s probably what you are seeing. Add a branch for Current Issue for each project, along with the appropriate condition under each branch (you can just use the issue…
-
Are the fields on the edit screen for the project? If you pull up the ticket itself, can you edit those fields manually?
-
Hola valeria, Puede incluir una transición de Cerrado a otro estado y llamar al nombre de transición Reabrir. Luego, establezca una condición para la transición de que el reportero pueda ejecutar la transición (junto con otros roles del proyecto, como el equipo de la mesa de servicio).
-
Hi Vamsi, I you don't need to populate the values in the form itself, you can easily populate the fields using an automation rule after the ticket is initially created.
-
-
It depends if you need to track whether it was the first approval or second approval, etc. You could probably get back with a single status if you like. You can make it work either way. I would tend to use the extra status though.
-
Hola Albert, Puede agregar un validador de campo requerido para la transición al estado. Esto asegurará que el campo esté completo antes de que se pueda realizar la transición del problema.
-
Hi Abir - Welcome to the Atlassian Community! I believe you are looking for an automation rule like the following:
-
Hi Nader - Welcome to the Atlassian Community! What is the Jira platform used by both companies? Jira Cloud? Jira Data Center? Jira Server? Feel free to connect with me in LinkedIn: https://www.linkedin.com/in/john-funk-92261a38/
-
Hi Mike - Welcome to the Atlassian Community! What exactly is your process and what exactly are you wanting to do and when?
-
Hi Dennish, You can only do that with a Move function, and that function is not available with Automation. You must do a manual Move.
-
Hi Shamara - Welcome to the Atlassian Community! I would use a board versus a calendar for that. You can create a board with a board filter that includes all of the projects. It would look something like: Project in (ABC, DEF, 123, 456)
-
Hi Kim, I would recommend creating a Jira Work Management Company-managed project. Click on the Projects menu at the top and select Create Project Click on Sales on the left hand menu Select the appropriate template - maybe Lead Tracking or Sales Pipeline Be sure to click on Show More link and change the Project Type to…
-
Hi Kevin - Welcome to the Atlassian Community! If you have a project that you want to use as a model, then great. If not, create a "template" project by simply creating a problem and set all of the schemes the way you want them. Then as you create new projects, go through the normal process: 1. Click on Projects, select…
-
Hi Katerina - Welcome to the Atlassian Community! You can create an automation rule to do that. You can either have a manual rule that you execute from the initial ticket, or you could have the rule fire automatically when the first ticket is created. Since I don't know when you want it to be executed, I will go with a…
-
Hi Chris, Built-in approvals only show for Jira Service Management projects or Jira Work Management Team-manage projects.
-
The Condition is on the transition in the workflow. Edit the workflow, click on the line for the transition, and see if there are any Conditions there.