Skip to main content

Request Administrative Changes in Jira

This article applies to: JIRA


If you are a Jira Project Lead or Administrator or were previously a Jira Global Administrator and have requests related to New Projects, Jira Workflows, Issue Type or Screen templates or Custom Fields, please send an email to jira-backline@cornell.edu and include the following: 

  • Subject: Request for Jira administrative change or inquiry. 
  • Project Name. 
  • Description of request (please specify the specific area in Jira, some examples are issue types, screens, fields, workflows, project permissions, project import, etc.). 
  • Business case or reason for change. 
  • Project Lead or Project Administrator name (if requestor is neither, please copy into your request the Project lead or a Project Administrator on the Project). 
    • Administrative changes can only be granted to individuals within these two roles. 

Your ticket will be assigned to someone on the Jira support team who will review and follow up with you on your request.  Please plan ahead for your change, so that appropriate testing steps can take place. 

Jira global administrative access, at the recommendation of the Vendor, is limited to central Jira administration and support staff.   

The typical process scenario for implementing administrative changes will be: 

  • After receipt of your request and the steps above are complete. 
  • Administrative access is provided to the Project Administrator or Lead in the test environment. 
    • The Project Administrator or Lead makes the change in the test environment. 
    • The central Jira Support administrator reviews the change for appropriateness and global impact.
  • The central Jira Support administrator implements the change in the Jira production system. 

For routine low impact changes, like if you indicated you have a frequent need to create new projects or perform a bulk imports, the process above can be slightly modified as follows: 

  • After receipt of your request and the steps above are complete. 
  • Administrative access is provided to the requestor in the test environment. 
    • The requestor makes the change in the test environment. 
    • The central Jira Support administrator reviews the change for appropriateness and global impact. 
  • The central Jira Support administrator provides administrative permissions to Jira Project Administrator or Lead (based on a pre-defined list of prior Jira Global Administrators). 
  • The Jira Project Administrator or Lead makes the change in the Jira production system. 

About this Article

Last updated: 

Monday, April 29, 2019 - 9:27am

Was this page helpful?

Your feedback helps improve the site.

Comments?