Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-18663

As a user, I'd like to be able to use the Time Stamp field with my own values

XMLWordPrintable

    • 0
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      As a user, I'd like to be able to use the Time Stamp field with my own values.
      Currently, the Time Stamp gives only intervals of 30m to select and does not give an option to insert my own values, giving the wrong Time Stamp information depending on the business scenario for the field.

            [JSWCLOUD-18663] As a user, I'd like to be able to use the Time Stamp field with my own values

            Matthew Hunter added a comment -
            Atlassian Update - November 1, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Matthew Hunter added a comment - Atlassian Update - November 1, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Ert Dredge added a comment -

            I want to be able to automatically add the current time to a field on an issue when a particular status transition happens, specifically to record when development has started and when QA has started on an issue.  I tried putting {{now }}into a timestamp field, but it fails apparently because of this.  I don't really care about the 1 minute resolution, but I do care that I cannot use automation to put the current time into a timestamp field.  That's incredibly surprising.  The 30 minute resolution of the timestamp just seems arbitrary, though.

            Ert Dredge added a comment - I want to be able to automatically add the current time to a field on an issue when a particular status transition happens, specifically to record when development has started and when QA has started on an issue.  I tried putting {{ now  }}into a timestamp field, but it fails apparently because of this.  I don't really care about the 1 minute resolution, but I do care that I cannot use automation to put the current time into a timestamp field.  That's incredibly surprising.  The 30 minute resolution of the timestamp just seems arbitrary, though.

            terence added a comment -

            The values can be pre-configured, they just need to be finer grained. 30min intervals is far too limiting. 1 minute intervals would suffice

            terence added a comment - The values can be pre-configured, they just need to be finer grained. 30min intervals is far too limiting. 1 minute intervals would suffice

              Unassigned Unassigned
              dbraun@atlassian.com Douglas B (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: