Chapter 4. JIRA as a Platform
Overview
A common request that JIRA administrators receive is to use JIRA for
more than its current purpose. The typical case is that someone in one
group tells a different group that you can do that with JIRA, and
it’s already installed.
After all, a JIRA project is like a
spreadsheet with a line for each JIRA issue and a column for each field.
It’s true that JIRA can be used to track many different kinds of issues,
and Chapter 3 described how to
configure JIRA schemes to do just that.
This idea is, in effect, using JIRA as a
platform for different web applications or
vertical solutions
for each group of users. There might be
one such web application for Engineering JIRA projects, one for Customer
Support JIRA projects, and so on. Using JIRA as a platform in this way is
part of how it is designed to be used, but it does need a consistent
configuration approach to be successful. This is particularly true if
different groups don’t want to see any part of other groups in the same
JIRA instance.
However there isn’t much documentation on how to do this in a consistent manner. This chapter describes one way to do this using a worked example, and then summarizes this in the section “Summary”.
What Can Be Configured
For each pair of a JIRA project and issue type, we can change the following:
Which system and custom fields an issue can use, and whether they are required or not
The order in which custom fields appear on an issue screen
The workflow for an issue, including ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access