Skip to main content

Making a custom field mandatory for a specific project in JIRA

Often we have project teams seeking the addition of custom fields and request that it be mandatory for only their project. These projects essentially share the same JIRA workflow, issue type, field, permission schemes but have different screens to enable display of the new custom fields. Now comes the tricky part - making the custom field mandatory would start throwing up errors while creating issues in the screens where they are not even available -


Error while attempting to create an issue in a different project

I checked out discussions on the subject in Atlassian Community but most answers suggested having a different field configuration altogether. This was not really an option in my case - didn't want to add clutter. That's when I came across an option in the custom field configuration that allowed specifying the projects to which a custom field needs to be available -

Choose applicable context for the Custom Field
This resolved our issue entirely and we are now able to add custom fields and make them mandatory for specific JIRA Projects. 

Comments

Popular posts from this blog

Turning off a Dell Laptop Monitor: Keyboard shortcut(s)

I am someone who is particular about power savings and I don't leave appliances powered on when not in use. The same applies to computing devices - be it a smartphone or a PC/Laptop. I power off the desktop monitor when I step out for a tea break or hit Fn+F2 on my Lenovo laptop that turns off the display. Recently, I got a Dell Laptop and I was surprised to discover that Dell does not provide any shortcut to turn off the display. This led to some exploration and I found two ways to achieve that which are outlined below - 

Resolving INS-20802: Oracle Net Configuration Assistant failed error on Windows 10

I was all excited about the migration to Windows 10 until I had to install Oracle client 12.1.0.2 on it. The Oracle client installation used to fail miserably at the last stage with this error named INS-20802.

Nginx - Solution for 10060: A connection attempt failed because the connected party did not properly respond

I was in the process of setting up Nginx to serve as the reverse proxy for Nexus Repository Manager OSS. However, the Nexus repository started loading really slowly post this and used to repeatedly display disconnected and reconnected messages. The Nginx log file used to log the below error - <timestamp> [error] 3240#3632: *1 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: <ip address="">, server: <fqdn>, request: "GET /nexus HTTP/1.1", upstream: "http://[::1]:8081/nexus", host: "<fqdn>"