JavaScript tricks on issue fields
JIRA provides a lot of options to manage the various fields on an issue. Field configuration schemes, screen schemes, and so on, help the JIRA admins to show or hide fields, mark them as mandatory, and so on, differently for different issue types and projects.
Irrespective of how configurable these schemes are, there are still areas where we need to perform custom development. For example, if we need to show or hide fields, based on the values of another field, then JIRA doesn't have any in-built options to do so.
Then what is the best way to deal with this? It is always possible to create a new composite custom field that can have multiple fields driven by each other's behavior. But probably an easier way-that ...
Get JIRA Development Cookbook - Third Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
