•  
     
    story #17127 have inactive artifacts with “waiting for closure” status to be automatically closed after a number of day of inactivity configurable,
Description
Advanced User
have inactive artifacts with “waiting for closure” status to be automatically closed after a number of day of inactivity configurable,

save time in monitoring tech support artifacts but still having a customized client support (by closing only artifacts that have already been sorted).

Functional overview

The plugin will - within each tracker administration - have a feature to add one or many artifact changes that will allow to:

  • configure one open value (like "waiting for closure) and a number of day of inactivity.
  • configure :
    • a closed status value
      AND/OR
    • a warning/associated comment

Technical overview

  • We will use a System Event that will be listened every 24 hours with codendi_daily_start (at the same time as other System Events of tuleap daily-job) to retrieve and close inactive artifacts.
  • The actions will be executed by Tracker_Workflow_WorkflowUser.
  • We will need Vue.js to build a SPA.

 

Practical example

Every day the bot will:

  • retrieve artifacts with open value set and which have been inactives for n days (depending on the number of days of inactivity set)
  • make an action on these artifacts base on the configuration: change his status and/or add a comment to warn the project administrator ("Inactive artifact will be closed in two days." or "This artifact hasn't been updated for 20 days.").
Progress
Empty
Empty
Will not be implemented
References
Referencing story #17127

Artifact Tracker v5

epic #17125 Service clean up
Access Information
#17127
2020-09-29 16:48
Simiand Camille (csimiand)
2020-10-02 16:40
Thomas Gorka (tgorka)

Follow-ups

User avatar
  • Acceptance Criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance Criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes