Skip to end of banner
Go to start of banner

Transitioned by Users

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

The Transitioned by Users custom field is a calculated field that displays a comma separated list of usernames for any users who moved an issue through a specific workflow transition. It is a read-only.

Add a custom field

There are two paths for adding a JMCF custom field - through the My Custom Fields page or through the native Jira Custom fields page.

To create a new field through My custom fields:

  1. Log into your Jira instance as an Administrator.

  2. Click Settings ⚙️ in the upper right corner.

  3. Select Apps.

  4. In the left-hand panel, click Jira Misc Custom Fields.

  5. Select My custom fields.

  6. Click New custom field in the upper right corner.

  7. Give the custom field a name and, optionally, a description. Note: the maximum length of both the name and description fields is 255 characters.

  8. Select the JMCF field type and click Next.

  9. Follow the steps in the next section to configure your custom field.

To create a new JMCF custom field through the Jira custom fields page:

  1. Log into your Jira instance as an Administrator.

  2. Click Settings ⚙️ in the upper right corner.

  3. Select Issues.

  4. In the left-hand panel, click Custom fields.

  5. Click Create custom field in the upper right corner.

  6. In the Select a Field Type window, click Advanced.

  7. Select the JMCF field type you want to add and click Next.

  8. Give the custom field a name and, optionally, a description.

  9. Click Create.

  10. Follow the steps in the next section to configure your custom field.

Note: If you create a JMCF custom field using the native Jira custom field process, the new custom field will not calculate until its Contexts have been updated; this limitation applies even when the custom field is configured for the Default context.

Configure a new ‘Transitioned by Users’ field

If you added a JMCF custom field through the native Jira custom fields screen, see Edit a custom field, below.

Follow the steps above to add a custom field to your Jira instance, then follow these steps:

  1. In Associate Screens step of the wizard, check the boxes for the screens to which the field should be added.

    1. Use the search field above the list of screens to locate a specific screen.

    2. Check the box at the top of the column to add the field to all screens.

  2. Click Next.

  3. Set the status value or values for both Transition From Status and To Status. When an issue is set to one of the status value(s) selected, it trigger an update of the Transitioned by User field.

  4. Click Save.

Note: The *ANY value for Transition From Status and/or To Status can have unintended consequences if not used correctly:

  • Setting both fields to *ANY will track any change in status for the issue.

  • Setting Transition From Status to *ANY will will track any transition into the status value(s) set in To Status no matter the starting status value.

  • Setting To Status to *ANY will will track any transition from the status value(s) set in Transition From Status no matter the starting status value.

You are viewing the documentation for Jira Cloud.

Switch to Jira Server/Data Center.

On This Page

Edit a custom field

There are two ways you can access a custom field to edit its configuration after it has been created:

  1. From the My custom fields page of JMCF Administration, click Action (blue star) and select Edit. Update the name and description, add or remove projects and issue types, add or remove screens, and update the JMCF configurations described below.

  2. From the Jira Custom fields administration page, click Action (blue star) and select an option:

    1. Edit details - Update the Field Name, Description, and Search Template for the field.

    2. Contexts and default value - Add or remove contexts for the field. Additionally, configure the Default Value and access the Custom field config to set the JMCF configurations described below.

    3. Translation and options - Set the language in Choose Language, then enter the Field Name and Description for that language.

    4. Associate to Screens - Add or remove Jira screens on which the field will appear.

    5. Move to Trash - Remove the custom field from all screens and move it to the Trash.

Custom fields can be recovered from the Trash for 60 days. After 60 days, the field will be deleted permanently and cannot be recovered!

Search templates

Currently, there are no specific search templates for custom fields created with JMCF; currently the only search template available is Forge custom field searcher, the default search template for Jira Forge apps. Because JMCF uses native data types, the fields are generally searchable using JQL and basic search. However, there are some differences between search in Jira Data Center and Jira Cloud:

  • Time in Status values are stored in seconds, but can be searched using a variety of representations, including by number of days (days or d), hours (hours or h), minutes (minutes or m), and seconds (seconds or s). This includes combinations of these units. Some examples include:

    • 2days3hours42minutes17seconds

    • 2d3h42m17s - 2 days, 3 hours, 42 minutes, 17 seconds

    • 7h15m- 7 hours, 15 minutes

    • 485903 - 485, 903 seconds

For example, the JQL query TimeInCurrentStatus > 9h30m will search for all issues with a value greater than 9 hours 30 minutes (34200 seconds) in the field TimeInCurrentStatus.

Search template flexibility will be expanded in later versions of JMCF for Jira Cloud as the Forge team introduces more capabilities for search.

  • No labels