Restrict time entry against "Closed" tasks

Gathering Feedback

Comments

12 comments

  • Avatar
    Ross Ellerington

    +1 for this. 

    1
    Comment actions Permalink
  • Avatar
    Santanu Mitra

    Hi,

    Any update on this?

    0
    Comment actions Permalink
  • Avatar
    7pace tech support

    It's planned later this year: https://support.7pace.com/hc/en-us/articles/360000233723-Feature-Roadmap it is a part of Rules and permissions.

     

    Maxim 

    0
    Comment actions Permalink
  • Avatar
    Magnus Schroder

    I hope that it will be possible to add restrictions not only based on status (i.e. Done and Removed), but also work item type and other details that may be applicable. We need the time to be reported at the task level, so it bubbles up through the system

    2
    Comment actions Permalink
  • Avatar
    7pace tech support

    Hi all!

    Could you please provide your feedback on this case:

    I have a Task item, it is closed and already has some time tracked on it. It turns out that I've logged incorrect time and would like to fix time record. Will it be possible?

    So the questions are:

    1) Should we forbid any time manipulation with closed items?

    2) Should we forbid only ADD/track of time, but edit operation of already existed tracks is allowed?

    3) Should "Closed/Removed" state be hierarichally checked (if Task is not closed, but direct parent is closed)?

    Regards,

    Andarth

    0
    Comment actions Permalink
  • Avatar
    Santanu Mitra

    Hello Andarth,

    In my understanding, time ADD/EDIT should NOT be allowed against “Closed” work items.

    Now to resolve your query, I think there can be an option (check box) in the Settings page like “Allow Time Entry for Closed Item”. This should be unchecked to restrict user to entry time against “Closed” items.

    Now someone has made an incorrect time entry against an work item. The work item is marked later as closed and after that the incorrect entry is found out. In this situation, the above mentioned check box can be ticked temporarily by the administrator/global approver so that the person can rectify the incorrect entry. Once done, again the check box needs to be unchecked.

    I think in this way we can manage flexibility.

    Additionally, it will be great if restriction to enter time against work item type can also be made available. This has already been clarified previously by Magnus Schroder.

    Best Regards,

    Santanu Mitra

     

    0
    Comment actions Permalink
  • Avatar
    7pace tech support

    Thanks, I'm in the designing process of this feature, so all feedbacks are very appreciated 

    >In this situation, the above mentioned check box can be ticked temporarily by the administrator/global approver

    And what if it is a large company (200-500 users, or even large)? In such a situation, it could be an annoying problem (admin will switch this checkbox several times a day).

    1) The solution could be 2 checkboxes (one to restrict only adding time, second to block also editing). But it will look like a mess, so I don't like it.

    2) Another solution is to reopen Item, edit time entry, close Item again. But it is also not the perfect solution.

    3) Any other solutions?

    And I would like to check your feedback on: Should "Closed/Removed" state be hierarchically checked (if Task is not closed, but the direct parent is closed)?

     

    >restriction to enter time against work item type

    yes, it is also on my desk, but I almost have no questions on it and let's discuss it not in the current thread :)

    Regards,

    Andarth

    0
    Comment actions Permalink
  • Avatar
    Matt Hobbs

    My recommendation is that the list of selectable items on the time record should be managed by a setting, e.g. Allow time to be recorded against these statuses" - the required Statuses will be selected by the Organisation.

    Excluding "Closed" "Done" etc from the Allowed list will exclude them from the list of available Work items.  If there is a need to record time against an excluded item simply change it's status, temporarily, in DevOps.  I believe this will simplify the approach/Solution for 7Pace.

    1
    Comment actions Permalink
  • Avatar
    Claudia Klahn

    I like the recommendation about the list of selectable item on the time record. But I don't like the approach of change status of items just to book time. 

    I'd prefer a role based solution like administrators should be able to book time on closed items. So users who approve the booked time of the employees of a company are able to add / move time to closed items if necessary. 

     About the hierarchy: It shouldn't be possible to close a story when one or more children are still oben. Or do I understand something wrong? For me it makes no sense to close a parent and leave the child open.

    0
    Comment actions Permalink
  • Avatar
    Catherine Beaudo

    We would like automated time tracking to stop when a work item is closed. This would work similarly to the way time tracking stops when I switch tasks. 

    I would like to maintain the ability to adjust time on the task at least within the same time period.

    0
    Comment actions Permalink
  • Avatar
    Nico Lachmuth

    Hi. Any update for this feature request?

    We currently having a request about disabling the possibility to track times on done/closed work items within our company. It would be nice if you could provide some infos if this feature is planned. Thanks. 

    0
    Comment actions Permalink
  • Avatar
    dev

    Hi guys,

    First of all, thank you for your ideas, they're really valuable for us.

    Claudia, great idea about the role-based solution. Regarding the hierarchy and parent-child states dependency - it's not a part of our product, we can't handle it. You'd better ask DevOps support about it.

    Catherine, good wish about automaton. We're not sure it's possible, because we need some special integration interface by DevOps to make it notify 7pace Timetracker about the state changes. We'll investigate this possibility.

    Nico, this feature is in our year plan. It's not exactly our priority now, we have some other features to do before. But it's planned to be implemented later this year. This is going to be a part of the Rules feature.

    Kind regards,

    Roman

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk