Best way to configure when you have a wide range of required fields

Jeffrey Bistrong

I got this spreadsheet from my DevOps team for a bit more structure around their jira tickets because a lot of them are missing a lot of critical information on their requests.

Trying to figure out the best way to configure this with the least amount of overhear. I am thinking about setting this up with JSM forms and then one the ticket is created move/clone it into the appropriate project and close the original one if needed. Curious if anyone has any other suggestions on a good way to configure this.

 

Olha Yevdokymova_SaaSJet

Hi @Jeffrey Bistrong,

If you're looking to collect structured, required data across multiple projects with minimal overhead, you might want to check out app developed by my team  Smart Forms for Jira.

Here’s why it could be a great fit for your setup:

Supports Required Fields – You can enforce mandatory fields at the form level, ensuring critical info is never missed.

Regex validation: Ensure all your input is in correct format with advanced regex validation, or simple characters or numbers limits

Clone-Friendly – When issues are cloned or moved, the attached forms and their submitted responses (or drafts) are copied too—no data lost in transition.

Draft Mode – Users can save form drafts before submission, which are preserved across issue movements.

🌐 Cross-Project Compatibility – Works seamlessly across Jira Software, Jira Service Management (JSM), and Jira Product Discovery (JPD).

🧩 Flexible Form Actions – Use a single form to:

• Create new issues (in the correct project with the correct issue type)

• Update existing tickets

• Share externally (via link, Confluence, website)

• Or simply collect detailed input within a parent issue

This way, you can configure one central intake process with strong validation, then route or replicate it into the appropriate team/project without missing any key information.