@Guillermo Rosas, we are going to need more info here. Please explain the use case. Under what conditions do you want to change the issue type. For example...
I want to automatically change the issue type from Bug to Improvement when Component is New Feature.
Thanks for your response, In that case, when there is an specific request participant.
To explain better I will give some features how do I use servicedesk:
Most of our customers creates a case through email channel, and there are 2 big types: 1. technical support for customers (support) as a default issue and 2. Selling information for potential customers (selling), each one follows a diferent workflow (so a different issue type).
Also I set a different email channel for each case: email@example.com for support (main) and firstname.lastname@example.org for selling (alias).
So, when a potential customer sends an email to email@example.com requesting information for our products, servicedesk creates the case keeping the alias (firstname.lastname@example.org) as a request participant.
To separate those selling cases and prevent them from mixing with technical support cases, I made an automation rule that changes the "customer request type" if the case have email@example.com as a request participant and it is separated in the respective queue, but the issue type is not changed, it keeps only in "support" then our sells staf has to change manually the issue type (but it is not practical because they have to change more than 100 cases each day)
So I would like to create an automation rule to change the issue type if there is "firstname.lastname@example.org" on request participant.
I'm still not quite sure I understand. Do you have a single project or two projects (support, selling)? If not why not is sure seems that they should be different projects. If a single project how do you have two emails feeding it? Maybe this is server and server allows that but didn't think so.
It is only one project, I set two emails and create a rule to separate each type, that is explained in this question:
My doubt is if it is possible to create an automation rule to change the issue type if there are some conditions, f.e. an specific request participant.
ah yes I recall that discussion. To be honest I think that method might lead to more issues down the road but that isn't based on anything more than a feeling so fell free to toss that comment aside. :-)
you can most certainly change the issue type based upon various conditions. it may require a plugin though. Unsure if this is one of those situations or not.
Can you take a screenshot of your current automation so I can have a look and offer my thoughts?
The desire to change an issue type is usually indicative of a broken process. It should really be reserved for genuine "clicked the wrong one" or "I completely misunderstood the type names" cases, and hence something you would normally do manually.
Two projects is a good solution.
@Nic Brough On Jira Server with Service Desk, we're ingesting emails into the service desk project. They come in via the email channel and are assigned an issuetype - I don't see a way to have multiple choices there. We have a certain type of email that arrives from an alert system - let's call it failed orders, that needs to be escalated to a scrum team (in their project). We have a workflow that does all the right things (with the help of scriptrunner - create a linked issue in a new project and set the proper assignee), but we need to get that ingested email/issue over to the right issuetype to follow that workflow.
Currently, our service desk agents are moving the issuetype manually, and it seems like this should be something we automate. Any thoughts on how to improve this process if we can't do it in a relatively simple way with a post-function?
The automation rules, as far as I can tell, only allow changes to the Request Type, NOT the issue type. I have the exact same scenario as David above, where I need notifications from some alert systems to come in as incidents instead of service requests. I am not able to do this that I can see, and it's a manual issue. It needs to be automated because the SLA for incidents is so different.
@Bethany Amborn I started creating related tickets in other projects which, when complete, transition the linked issues in service desk. Now...to keep things from messing up, I created a unique set of “relates to” so there wouldn’t be an impact on other linked issues.
I’ll take a peek back and see if there’s something new since we’ve upgraded to jira 8. But yeah, it’s still a problem.
If not, and what I’m doing sounds useful, I’m happy to share the workflow with you.
Oh, and we got it there by creating an escalate to each scrum/infrastructure team “Status” that creates the linked issue in their respective projects - forgot that part. That way we know what’s in the other teams’ courts without messing about in other projects and leaving ours.
Hi all! We’re interested in learning more about your ITSM practices - what’s the current state of your ITSM practices? What are your aspirations for your IT team in the future? Which ITSM trends ar...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events