nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I create customize form for each of my issue type?

Jacqueline N McCluer

I would like to create a customize form for each of my issue type. For Example, I would like a specific form when creating Epic issue type vs when I create a bug issue type. So that users can fill out the following information when they create those issue type. I am currently using the classic project.

Accepted answers

All comments

Brant Schroeder

@Jacqueline N McCluer

Welcome to the community. You will need to create a different create screen for each of the issue types. You will then need to then update the projects screen scheme and associate those screens with the issue types in the project. Helpful documentation below.

https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-type-screens/

https://support.atlassian.com/jira-cloud-administration/docs/manage-screen-schemes/

Jacqueline N McCluer

Thank you for your help. I will follow the instruction and reach back out if I have future questions.

Jacqueline N McCluer

@Brant Schroeder will this interfere with other projects that are using the same issue type as me? or this screen would only apply to my project setup?

Brant Schroeder

Just make sure that the screen scheme you use is unique to your project and it will not have any impact on other projects.

Jacqueline N McCluer

@Brant Schroeder I want to clarify my question above. I would like the have a custom form of an epic issue type in the description and not the issue layout with different field. the below image is that I am trying to accomplish in classis project setting. the image below is in Next-Gen project setting. Please let me know if I can create something similar in classis project Screenshot 2021-01-20 115027.png

Brant Schroeder

You would have to use next-gen for that functionality in the description field. You would need to convert the classic project to next-gen. (migrate)

Jacqueline N McCluer

thank you @Brant Schroeder

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud