Thanks for the feedback, I've updated the article. :)
And yes, it is absolutely toggled on by default. We really want users to see the request type configuration in the issue create experience but acknowledge that this doesn't yet meet the needs of all users.
Appreciate the feedback on having a preference for a project level toggle. We were worried that would be less discoverable and not cater to cases where a user needed to see a different end user experience per request type (i.e. create screen vs. request type configuration).
In any case, the idea is that we remove this toggle in the future once we've found a way to better solve the challenges our customers are facing here.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Thank you @Jehan Gonsalkorale - I dont think it is a need to "remove this toggle in the future" as it does imply the need for it esp with the number of fields differing between create screen vs. request type configuration - it just needs to be more configurable (required/not required/disabled but shown) but that is my thought :D
Thank you for the feedback and the community consideration!
@Chris UggenI've used "build your own scripted" validator from JMWE to enforce changing the request type. I know we shouldn't have to subscribe to an app to accomplish this, but if that's an option for you or if you already have JMWE, that's one way to accomplish what you mentioned.
It would be great if the admins could no only decide which Request Type is viewable in the Portal (feature exists today) but also which Request Type is viewable under/in/via the "Create" button (for example, we cannot hide the "Email" Request Type from the "Create" button.
We are definitely aware of this feature request and are hoping to prioritise it in the medium to long term. We are currently focusing on making request types and workflows easier to configure, given that customers are often confused by screens and schemes (so we want to make it possible for them to work without them).
That said, this is a high value feature that we do want to deliver, we just need to get through our current focus areas first.
I was just wondering if there's any update on the full compatibility with Forms in this create issue experience. If there is a Suggestion ticket I should be watching instead, please refer me to it.
We want an admin option to turn on/off the display of the "Use Request Type Fields" toggle bottom in the creation screen. Some users complains of the activated status of this bottom.
34 comments