Hello community,
I created a request type, attached a form to this request.
When create an issue with this request type, I have a message saying that "This request type includes a form that can’t be seen in this view. Create an issue using all fields on this request type and its form in the portal."
When click on the portal, it works well.
Thinking that is a display problem in the form attached, I replace the real form with a blanco form -> same message.
Thank you in advance.
Hi @Han LE ,
Welcome to the Community.
There is no error in the form. This is default behaviour.
Forms in Request Types are not displayed like in the portal. In the backoffice, you will only see the fields that are defined in the request type, outside the form. That's why you see this warning message.
Therefore it's always advised to create JSM tickets via the portal.
You can still create the ticket in the backoffice, but you can only enter the form AFTER creating the ticket. In the ticket detail view, click on the "Add Form" button to add it.
Best regards,
Kris
Hello Kris,
Thank you for the information. I didn't know it's a normal behavior.
I just want to attach directly the form in the ticket so users don't have to.
We will then use only the portal for this request type.
Regards,
Han
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Honestly, this is pretty poor UX. My agents don't want to have to switch back and forth between the portal and the "backoffice" just to submit tickets on behalf of the users. Maybe we can get someone from Atlassian to report on whether they are working to change this behavior.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Happy New Year, @Travis Cochran. Welcome to the Atlassian Community.
I'd like to point out that you shared your feedback to Atlassian as an "answer" to @Han LE question. Since it's not really an answer to his question, that's probably not the right approach.
First, the community is largely comprised of Atlassian customers/users, like you. While someone from Atlassian may see your feedback, it's not guaranteed.
The best way to make such suggestions is via "Suggestions and bug reports" — for the appropriate Atlassian product (in this case Jira Service Management) — in the Atlassian support portal.
I did a quick search but did not find any related suggestions. You may want to create one.
Meanwhile, I'll share a link to your post with some of my Atlassian contacts.
Best,
-dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.