Hello, I would like to create a rule which allows new tickets created from a ticket to be added to the request type. I tried to do it but couldn't. Can you help me please ?
Hello @Kevin Vancrutsen
Can you elaborate more on this? When you are creating a ticket, either from the portal or from the agent view, it will be created based on the request that was chosen. This is the default behavior. Each request type is also tied with an issue type.
It's from the agent view. When you create linked issue, you can't see the request type field. If you proceed the creation of ticket, the field is empty. I want a rule to set the de request type automatically when a issue is created like that
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Work items are not meant to work in that way. Work item links are based on the inward and outward linking descriptions.
Work items are not the same as Request types. Rather request types are dependant on the work items.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nikola Perisic is right here.
Then you could create an automation after this action.
That fires on work item creation and and set condition that apply, based on link type and then use the set Request Type action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, thanks for ur reply. I will clarify my request. When one of our agents processes a ticket, we may need to create a child ticket, and we use the “create linked issue” feature, which automatically links the two tickets together. When creating the child ticket, the window does not allow you to choose the request type for the selected ticket type (we have ticket types such as incident, service request, change, etc.).
I am happy to automate this task, but I want it to be used specifically and only for this case. That is why I am looking for the most suitable trigger.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bonjour @Kevin Vancrutsen
Ton automatisation se déclenche lorsqu’un utilisateur de ton projet crée un ticket via la fonctionnalité Linked issue.
Si le besoin est de mapper ce ticket avec un Request type de Jira Service Management :
Tu n’as pas besoin de créer une branche sinon ca va faire les actions sur le ticket du branche et pas ce ticket
je suggere d' ajouter une condition pour vérifier si le ticket possède un lien de type (afin de cibler uniquement les créations issues de cette action).
Ensuite, ajoute action Edit request type et lui attribuer le Request type de ton projet.
⚠️ Assure-toi que le type de ticket correspond bien au Request type, sinon l’automatisation renverra une erreur.
Voici un exemple
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Kevin Vancrutsen ,
Here I need a bit more information to understand whether, when you create a ticket, you would like to generate other linked tickets, or if instead you need to create subtasks under the main task you are creating.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Kevin Vancrutsen ,
You need to use this automation rule. First, use the action Create work item with a request type, and then link it to the most recent work item.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Pedro Olmo
Is the request type will be shown on the linked work item. Not the work item itself, rather the request type?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.