Siddesh BG's Build Release Config mgmt Blog

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 25 May 2012

Jira Administration - Custom Fields & Screens

Posted on 00:19 by Unknown
Jira has a complex administration concepts. Performing Jira admin tasks without understanding the complete flow leads to mistakes. In this post, I'm explaining how the Custom Fields are created and how to link it to project screens.

Creating custom fields
Let's assume you get a request to create a custom field "Severity". Check whether this custom field is already existing by

  • Login to Jira -> Administration -> Issue Fields -> Custom Fields
If it is not available, create it straight away

    • Login to Jira -> Administration -> Issue Fields -> Custom Fields -> Add custom Field -> Choose the field type -> Provide field name, search template, etc , applicable issue types, Applicable context.
   Custom Field Context
        The custom field which we created can be associated to all issues by selecting "Global context" or to specific projects. Depending on the usability of the custom field make it either global or project specific.

If the custom field is already exist, then try to reuse it.

Screens
Screens group multiple issue fields. Using Screens, you can control which fields are displayed. You can also split fields on a Screen into multiple tabs.


Configuring/Adding screens
  • Login to Jira -> Administration -> Issue Fields -> Screens
You can define/edit screens with the above steps. 

How the screens relates to a project ?  [Screen -> Screen Schemes -> Issue Type screen schemes]
  A Screen Scheme allows you to choose which Screen will be shown to a JIRA user when they perform a particular issue operation (like Create Issue, Edit Issue, View Issue). You can specify the same screen for each of these issue operations, or choose different screens for each operation.

Creating/Configuring Screen schemes
  • Login to Jira -> Administration -> Issue Fields -> Screen Schemes -> 
Here associate an Issue operation to a screen.

Linking screen scheme to projects
To activate a Screen Scheme, you need to associate it with one or more projects and issue types, using Issue Type Screen Schemes

An Issue Type Screen Scheme associates a Screen Scheme with issue types, allowing you to specify different Screens for the same operation (e.g. 'Create Issue') in the same project for issues of different types.

Create/Edit Issue Type Screen Schemes

  • Login to Jira -> Administration -> Issue Fields ->  Issue Type Screen Schemes

The configuration of an Issue Type Screen Scheme involves associating an issue type(s) with a particular Screen Scheme. For example, associating the 'Bug' issue type with the 'Default Screen Scheme' and then associating the 'Improvement' issue type with the 'Improvement Screen Scheme'.

Associating an Issue Type Screen Scheme with a Project: Login to Jira -> Administration -> Select the project of interest -> Issue Type Screen Scheme -> Associate


How to add a Custom field to a screen ?
Find out the "Issue type screen scheme" your project is using Jira -> Administration -> Select the project of interest -> Issue Type Screen Scheme  -> Edit ( Here you will get to know about your screen scheme) -> Click your screen scheme [It will list the screens ]-> Select the screen -> Add Field  -> Add

Is your new custom field still not showing up on the desired screen ?

  • Check  whether the field is hidden in Field configuration
           Login to Jira -> Administration -> Issue Fields -> Field configurations  -> Click configure of the desired field configuration scheme -> It will list all the fields for your project -> If the needed field is hidden, then click 'show' 

  • Check whether your custom field context is restricted to specific projects 
     Login to Jira -> Administration -> Issue Fields -> Custom Fields -> Choose the custom field of interest -> Configure -> Edit Configuration -> Choose applicable context. 

      If it is restricted to specific project, then you can 
  1. Add your project also
  2. Or change it to 'Global context'
        Be careful and don’t configure a existing custom field to a project. This will then limit the custom field only to that project, removing it's visibility on other available screens.

How to know which projects/screens use a given custom field ?
  Login to Jira -> Administration -> Issue Fields -> Custom Fields -> Choose the custom field of interest  

 If the custom field 'Available context' shows any project, then it is restricted to that project. If no projects is listed in 'Available context', then look at the screens it is associated. A screen will be associated to a project through Screens -> Screen Schemes -> issue type screen schemes
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in Jira | No comments
Newer Post Older Post Home
View mobile version

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Solution to Project Euler Problem 10 - Find the sum of all the primes below two million
    http://projecteuler.net/problem=10 Problem The sum of the primes below 10 is 2 + 3 + 5 + 7 = 17. Find the sum of all the primes below two mi...
  • Fortify scan automation steps for analyzing c/c++ code (Makefiles)
    I wrote in my previous blog about installing and configuring Fortify client. This blog presents standard steps to automate fortify scan for ...
  • Posting a JIRA bug using Perl Mechanize
    Perl provides modules which can be used as command line browser to automate tasks dependent on web pages. Among them LWP and mechanize are i...
  • jenkins error: java.io.IOException: Authentication method password not supported by the server at this stage
    When I tried to add a node to jenkins/hudson using ssh as launch method, the authentication keeps on failing with the below error. [12/15/11...
  • Unable to resolve target system name - a DNS problem
    I was not able to ping to any machines from my Windows 2003 server. I did following steps to debug & resolve the issue, which was relate...
  • Installing and configuring Fortify on Linux and Windows machines
    Installing Fortify on Linux (RHEL 5 32 bit) Download Fortify archive Fortify-360-2.6.5-Analyzers_and_Apps-Linux-x86.tar.gz and extract it to...
  • Perforce - can't edit exclusive file already opened
    In perforce, whenever a binary file like doc, xls or ppt files are checked out, it is opened in exclusive lock mode. So no other person can ...
  • Perforce and cygwin
    Are you a command-line freak ? Do you want your automated shell scripts to run on Windows ? Do you wish to work with Perforce commands on Cy...
  • Using BUILD_LOG_REGEX in jenkins email notification
    Jenkins provide 'Email-ext' plugin, which  allows to configure every aspect of email notifications. One of my requirement is to send...
  • 0509-036 Cannot load program p4 because of the following errors
    Here is the full description of error ............ bash-3.00# p4 info exec(): 0509-036 Cannot load program p4 because of the following error...

Categories

  • AIX
  • AIX ssh
  • ANT
  • apache
  • appliance
  • awk
  • branching
  • build-failures
  • cgi-perl
  • code-signing
  • commands
  • continuous Integration
  • cvs
  • cygwin
  • DNS
  • Drupal
  • EPM
  • euler
  • Fortify
  • hadoop
  • hpux
  • html
  • InstallShield
  • iptables
  • iso
  • jenkins-hudson
  • Jira
  • kiwi
  • linux
  • Makefile
  • maven
  • Miscellaneous
  • mysql
  • nexus
  • NFS
  • package
  • Perforce
  • Perl
  • php
  • rbuilder
  • rpath
  • rpm
  • rsync
  • Solaris
  • ssh
  • SuseStudio
  • tinderbox
  • unix
  • Visual studio 2008
  • vmware
  • war
  • webserver
  • wget
  • windows
  • xterm

Blog Archive

  • ►  2013 (12)
    • ►  December (1)
    • ►  July (2)
    • ►  April (2)
    • ►  March (2)
    • ►  February (3)
    • ►  January (2)
  • ▼  2012 (43)
    • ►  December (2)
    • ►  November (1)
    • ►  October (4)
    • ►  September (7)
    • ►  August (5)
    • ►  July (4)
    • ►  June (2)
    • ▼  May (3)
      • Jira Administration - Custom Fields & Screens
      • Issue: Nexus is too slow in downloading pom files
      • ssh command run from Jenkins shell will take “/” a...
    • ►  April (4)
    • ►  March (3)
    • ►  February (1)
    • ►  January (7)
  • ►  2011 (23)
    • ►  December (4)
    • ►  November (9)
    • ►  October (4)
    • ►  September (1)
    • ►  June (2)
    • ►  May (1)
    • ►  April (1)
    • ►  March (1)
  • ►  2010 (15)
    • ►  December (2)
    • ►  November (1)
    • ►  September (3)
    • ►  April (1)
    • ►  February (6)
    • ►  January (2)
  • ►  2009 (28)
    • ►  November (5)
    • ►  October (3)
    • ►  September (2)
    • ►  August (1)
    • ►  July (1)
    • ►  June (5)
    • ►  May (3)
    • ►  April (1)
    • ►  February (2)
    • ►  January (5)
  • ►  2008 (20)
    • ►  December (6)
    • ►  November (3)
    • ►  October (1)
    • ►  September (1)
    • ►  July (8)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile