Remaining Estimates and Logging Work

XMLWordPrintable

    • Severity 3 - Minor
    • Hide
      Atlassian Update – 11 October 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 11 October 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      There are 2 issues that appear to be going on here....

      The 1st issue - Remaining Estimates (Create an Issue)

      When I create a new or edit an Issue, and I try to set the Remaining Estimates to "Leave Estimates Unset", the radio button for Leave Estimates Unset is chosen. However when I go to log work, I am getting an error that states 'Remaining Estimates is Invalid".

      If I go back into the edit mode of the Issue to see if my setup is still set on Leave Estimates Unset, I see that is has changed to Adjust automatically. It is not saving my choice selection.

      The 2nd issue - Log Work

      When I choose the Log Work and I make my entries into the pop-up box, if I put "0" in the Remaining Estimates field, they system auto changes that entry to display "N/A".

      However, if I delete the N/A and reenter the "0" again, they system takes that entry and I am able to log work. Is this a current bug issue or does this currently work this way?
      This appears as a bug with a workaround to remove the N/A and enter the "0" or whatever value to be able to proceed further.

      This does not matter is I config my screen to display the log time fields when a user creates an Issue or not

            Assignee:
            Unassigned
            Reporter:
            Micky INS
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: