Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-71384

Misleading Time in Status custom field type

XMLWordPrintable

      Summary

      In Jira cloud, the [CHART]Time in Status which is using the customer field type Time in Status is used for reporting in average time in status gadget. Within the custom field configuration, a user is allowed to create a custom field using the Time in Status type. This can further be misinterpreted as a standard field type containing data that is user readable.

      Steps to Reproduce

      1. Create a new custom field
      2. Choose the type Time in Status.

      Expected Results

      Time in Status should not be configurable as this field type is not meant to contain data that can be directly used by end users.

      Actual Results

      Time in Status can be configured and further be added to screens. The actual field created cannot be edited nor viewed.

      Note

      JRACLOUD-60841 is the existing feature request to actually allow reporting of time in status for individual Jira issues.

        1. image-2025-02-17-16-48-54-091.png
          image-2025-02-17-16-48-54-091.png
          399 kB

            [JRACLOUD-71384] Misleading Time in Status custom field type

            Isai Navarro added a comment -

            https://getsupport.atlassian.com/browse/JST-1073160

            Isai Navarro added a comment - https://getsupport.atlassian.com/browse/JST-1073160

            Ostin Hops added a comment - - edited

            The Time in Status app allows you to create a custom field that will calculate the time in status. Your custom field will be created with read-only and configuration-blocked settings. Try it, I hope it will be useful for you.

            Ostin Hops added a comment - - edited The Time in Status app allows you to create a custom field that will calculate the time in status. Your custom field will be created with read-only and configuration-blocked settings. Try it, I hope it will be useful for you.

            Megha added a comment -
            Atlassian Update - October 28, 2020

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Megha added a comment - Atlassian Update - October 28, 2020 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              rmacalinao Ramon M
              Affected customers:
              30 This affects my team
              Watchers:
              39 Start watching this issue

                Created:
                Updated: