Column-Specific Configuration:

The Auto Archive Task feature can be enabled or disabled for each column in the board.

When enabled, you can specify the number of days a task must remain in that column before it is automatically archived.

Example Scenario:

Suppose you configure the Done column to archive tasks after 2 days.

If a task is moved to the Done column, GitScrum will monitor its status. After 2 days, if the task has not been moved to another column, it will be automatically archived.

Customization Options:

You can set different archive durations for different columns based on your workflow needs.

For example:

Testing Column: Archive tasks after 3 days if no further action is required.

Review Column: Archive tasks after 5 days if they pass the review process.

Disabling Auto Archive:

If you prefer manual archiving for certain columns, simply disable the Auto Archive Task feature for those columns. This gives you full control over which tasks are archived.

Access Column Settings:

Click on the column name or settings icon to access its configuration options.

Enable/Disable Auto Archive:

Toggle the Auto Archive Task option to enable or disable it for the selected column.

Set Archive Duration:

Enter the number of days a task should remain in the column before being archived. For example, set it to 2 days for the Done column.

Save Changes:

Once configured, save the settings to apply the changes.

Reduce Clutter: Automatically archiving tasks keeps the board clean and focused on active work, improving visibility and productivity.

Save Time: Eliminates the need for manual archiving, allowing team members to focus on more critical tasks.

Consistent Workflow: Ensures that tasks follow a predictable lifecycle, from creation to archiving, maintaining order across all boards.

Preserve History: Archived tasks remain accessible for future reference, providing valuable insights into past work and performance.

Software Development

Scenario: In the Testing column, configure tasks to be archived after 3 days if no issues are reported.

Benefit: Ensures that tested tasks are automatically archived, freeing up space for new tasks without requiring manual intervention.

Marketing Campaigns

Scenario: Set the Published column to archive tasks after 7 days once content has been live for a week.

Benefit: Helps maintain a clean board by removing completed marketing activities while retaining a record of published content.

Event Planning

Scenario: Configure the Completed column to archive tasks after 2 days following the event.

Benefit: Keeps the board focused on upcoming events while preserving a history of past successes.

Support Teams

Scenario: In the Resolved column, archive tasks after 5 days if no further customer interaction is needed.

Benefit: Reduces clutter in the support queue while maintaining a log of resolved issues for future reference.

Define Clear Criteria: Establish guidelines for when and why tasks should be archived to ensure consistency across the team.

Monitor Archive Settings: Regularly review and adjust archive durations as needed to align with changing project requirements.

Communicate with the Team: Ensure all team members understand how the auto-archive feature works and its impact on their tasks.

Leverage Historical Data: Use archived tasks for analysis, benchmarking, and continuous improvement of processes.

A software development team uses GitScrum to manage their workflow with the following columns: Todo , In Progress , Testing , and Done .

Testing Column: Configure tasks to be archived after 3 days if no bugs are reported during testing.

Done Column: Set tasks to be archived after 2 days once they are fully completed and deployed.

When a developer moves a task to the Testing column, GitScrum starts tracking its time there. If no issues arise within 3 days, the task is automatically archived. Similarly, tasks in the Done column are archived after 2 days, ensuring the board remains focused on current priorities.