Use Cases
Whether you have a specific need to solve or want to explore the wider possibilities of JMCF, our use cases will help get you started. Included below are examples of our more common use cases with scenarios and step-by-step instructions. You can use JMCF to create custom fields, and use those fields in reports and dashboards to bring expanded functionality to your Jira instance.
To follow the use cases below, you will need Jira administrator permissions. It is expected that you know how to create and edit custom fields in Jira. If you aren’t familiar with creating custom fields, see Atlassian’s documentation for Jira Cloud Administrators. We recommend that you try out your rules in a test environment before publishing changes to live projects.
To help ensure that your JMCF custom fields work the way you and your team expect, build your custom fields in a test project first, with user permissions that represent the different roles within your team and a set of example issues with which to view each custom field results.
Date and Time
-
Date of Initial Fix — Show the date the issue was initially set to a specific status.
-
Display the Projected Due Date — Display the projected due date for an issue based on it’s priority.
-
First Approved Date — Display the date an issue was first moved through a specific status.
-
Last Time an Issue was Flagged — Show the user or users who initially moved an issue through a specific status.
-
Time Spent in 'Blocked' Status — Display the date and time when an issue had a specific field updated.
Numeric and Counts
Scripted
-
Display the Projected Due Date — Display the projected due date for an issue based on it’s priority.
User and User Groups
-
First Approver or Approvers of Issue — Display the user (or users) who first moved an issue to a specific status.
You are viewing the documentation for Jira Cloud.
Switch to Jira Server/Data Center.