Jehan Gonsalkorale Atlassian Team

Hi @Rubén Álvarez González , This feature will be available in "Project Settings" > "Request Types" within the project itself. Please sign up and let us know what you think! Best regards, Jehan

Hi @Haddon Fisher, I may have not have expressed myself very well here, apologies. Re-reading my reply, I definitely was not very clear. We are not removing screens and schemes and issue types in the foreseen future, we are simply removing them from the mental model of less experienced users. If I can compare to Microsoft…

Thanks so much @__ Jimi Wikman I really appreciate the kind words, I'll share it with the team. 

Hi @Haddon Fisher and @Patrik Korovsky I can provide some clarity here, this feature simply allows you to change the issue type of a request type. The only difference is that we are encouraging users to think about issue types as being synonymous with workflows. We are introducing a new feature this year that allows you to…

Hi @Pramodh M , Sorry about that, I've just updated it, you should be able to access it now. Excited to have you as a part of this! Jehan

@__ Jimi Wikman I saw that you signed up, you'll be given access in the coming days. We will be waiting for your feedback. :) 

@Jeff Guthrie, That's a very reasonable request. We are definitely looking at improving this experience further and this is a very good point. We considered a cascading list before but there were many customers who had a large number of issue types and a (relatively) small number of issue types. This made finding the right…

Hi @Michael Hart , Sorry for the very late response, i didn't see a notification for this. We have an early access program for this feature, please sign up here to get it enabled on your instance.…

Hi @Alex Koxaras -Relational-, Thanks for getting in touch! We are only releasing this for Company Managed Projects in Jira Service Management because they are the only project type that have issue types. Does this answer your question? Let me know if I've missed something. Keen to understand your needs as best as we can,…

Great questions as usual, @Dirk Ronsmans! Changing the issue type of a request type will update all existing issues. It's largely the same as creating a new request type on the issue type you want to change to and bulk moving all existing issues to it. The issue type / workflow terminology is about encouraging basic users…

Hi @Wasi and @Nuwanee Nadeesha , we really appreciate your feedback! The kind words are appreciated. We still want to improve this functionality in future, but this is an important first step. Best regards, Jehan

Hi @Aaron Clements, That is a very good question. There absolutely is. We are soon to release a Feature Lab feature that will allow you to set a default request type for issues per project. The first iteration will not cover the create experience as it is designed for ensuring that the request type is not lost when tickets…

Hi @Madhumita Katta , Sorry to hear that. We are working on a fix here, but I think it might be easier if we rolled back the request type configuration (you'll still get the Issue Type and Request Type drop downs). Could you email me at jgonsalkorale@atlassian.com ? I'd be more than happy to roll that part of the change…

Hi @Ammar Ahmed Butt , please get in touch! I'd love to talk to you. You can reach me at jgonsalkorale@atlassian.com Looking forward to hearing from you!

Hi @Clare Lawson , Thanks for raising this and sorry for the confusion. I'm the product manager that pushed these changes out. We're aware that we've created some end user frustration here and do apologise for that. Subsequent releases will involve more clear communication. The new request type field is intended to…

@Aaron Clements, That is a good question, but no. Rolling back this flag will not cause any data loss. We are currently not rolling the entire feature back, but simply the feature that surfaces the request type configuration in the issue create experience (when a request type is selected). This will typically solve the…

Hi @Alan L. , Really sorry to hear that. Could you please email me at jgonsalkorale@atlassian.com and share your instance's URL so we can turn if off? Same goes for anyone else who has been impacted, very keen to help you manage the transition and improve the experience for you. Best regards, Jehan

Hi @Desmond Cox, Sorry about the inconvenience we caused you, that was not the intention but what we can do is figure out how we can support you and improve the experience. Would you be open to having a chat with us? I'd love to see how we might be able to keep moving in this direction while making things easier for you…

Hi all, many of you have mentioned that you are having problems with the new experience. Please send me an email to jgonsalkorale@atlassian.com and give me an overview of how this is impacting your customers and what would be the preferred behaviour. Please include your instance url so I can disable it temporarily while we…

Hi @Rilwan Ahmed and @Pramodh M , I'd love to get in touch! Could you send me an email at jgonsalkorale@atlassian.com? Looking forward to hearing from you, Jehan

Hi all, the update is rolled out again and live with 25% of customers (the same 25% that had access to it before). I'll continue to update as we roll out to more tenants. Thanks, Jehan

Also, apologies in advance if you've already tried this. 

Hi @Kyra Mayock, This could be due to fields that are configured as "Required" in your request type configuration. Have you tried navigating the the request type configuration within the project to make sure there are no fields set as "Required" there? Both field configurations and request type configurations allow fields…

Hi @Wesley Bouwer, That is very concerning. Sorry to hear about this. Could you please email me the url of your tenant? We can turn it off tomorrow morning AEST while we figure out how to solve for this. If you can, please provide some information and/or screenshots about your configuration and use case so we have a bit…

@Dominik Březina Great suggestion, updating now :)

Hi @Todd Thomas, Unfortunately, at this point there is no standard process for us to communicate these things to you, but I definitely agree that something needs to be done. I've flagged this internally and will push for us to find a better solution. I can provide an update here and say that we are planning on rolling out…

Hi all, apologies for the rollback, we've noticed a bug where fields that are hidden via field configurations in global settings are appearing as required, meaning that tickets cannot be submitted. We are working through this bug and are hoping to push the new experience out again today. Sorry for the inconvenience, we…

@Hi @Peter, I may have found a workaround for you in the meantime. You can set fields to be "Hidden" and set preset values for them to be autofilled. This same functionality can be used for agent-only fields if you don't set a preset value. They will appear to agents in the create experience but not in the portal. Could…

Hi @Peter Not a problem at all, I appreciate your carefully thought out reply. :) I'll respond to each separately. * Two very good points. I've updated this page but do agree that we could have communicated this change with more warning. I'll look into how we can do this so changes don't arrive so unexpectedly. * Your…

Hi @Peter, I appreciate your feedback. We are looking to simplify this experience while enabling that use case, which we are well aware of. At the moment, you can deselect the request type and get the screen configuration rather than the request type configuration. This is the default behaviour for "Tasks" and the only…