Add Issues to the Library for Company-Controlled Issue Management and Enhanced Conditional Logic in Forms

[eirik.vollen]

Description:
Currently, when using forms with conditional logic, the issues must be manually included in each template. This creates a heavy maintenance burden, especially when the same forms and issues are reused across multiple templates.

I propose extending the library functionality to support issues, allowing issues to be centrally managed and included in forms via the library. When importing a form from the library that contains conditional logic tied to specific issues, those issues should be imported automatically or linked from the library.

This would significantly reduce duplication, simplify updates, and minimize the risk of errors when deploying or maintaining forms across multiple templates.

Benefits:

• Centralized management of issues and forms
• Reduced maintenance workload
• Easier implementation of new issues
• Lower risk of configuration errors
• Improved scalability and consistency across projects

Suggested Implementation:

• Allow issues to be stored and managed in the library
• Ensure conditional logic in forms referencing issues remains functional when imported
• Maintain backward compatibility with existing templates

[nikmohdzamri]

We completely agree regarding the Issue type setup. Currently, with approximately 300 projects in ACC, adding new standard Issue types requires us to update each project individually, which is time-consuming and prone to errors.

If Issue setup could be managed centrally in the Library—similar to how forms are handled—new Issue types could be assigned to all projects directly, streamlining the process and saving significant effort. 

@ameerul.rafei do you agree on this?

[sara.hendler]

Complete agree AND I would like to add that any Library-Form with conditional logic tied to a Library-Issue, upon importing to a project or project-template, to stay connected.