Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-13512

Setting remaining time to 0 in a post function of the workflow causes the original estimate to be set to 0 as well (only when no time was logged by the assignee)

XMLWordPrintable

    • 5
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      This situation has been mentioned on the Jira forum and comments in other issues.
      This causes serious problems with our workflow as it destroys the reliability of hour timesheet reports

      See this comment from JRA-1993:
      I wanted to use post-functions of workflows. I am setting remaining time to 0 there. Unfortunately I have the following problem: if nobody has logged any work till the moment when the issue is closed (or resolved) then this post-function in fact resets original estimation to 0 (instead of resetting remaining time). Our people often close issues and then report time spent. It means disaster for us - original estimations are erased.
      With the lack of support for logging work on transition screen - I cannot handle it.

              Unassigned Unassigned
              780dfc3d-dfbf-4311-af44-62fc07eb7ce7 Deleted Account (Inactive)
              Votes:
              69 Vote for this issue
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 16h
                  16h
                  Remaining:
                  Remaining Estimate - 16h
                  16h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified