Hello,
I've recently explored similar challenges in Jira regarding setting up recurring tasks. I want to share my approach and some insights that might be helpful.
NO THIRD PARTY APP Solution
Project Configuration for Recurring Tasks
- Task Visibility: Create a project where users only see tasks assigned to them or where they are the reporters.
- Workflow Adjustment: Adjust the workflow to allow tasks to move from a 'Done' state back to 'Backlog' or 'To-Do'. This approach facilitates the recurrence of tasks.
- Organizing Tasks: Implement swimlanes and quick filters based on the next follow-up date. This setup helps categorize tasks as past due, due today, remaining this week, or upcoming next week.
- Manual Task Management: At the end of the workflow, it's crucial to manually recognize recurring tasks and move them back to the 'To-Do' status. or add additional swimlanes and quickfilters so that done tasks still listed as recurring with a past due date show up in a specific swimlane or filter signally you to reset them back to backlog or todo. Or whatever status you want.
Limitations and Risks:
- Any user accessing the issue can change the next follow-up date field. I've instructed my team to allow only the assignee to change the field. We mostly honor this; sometimes, we have a mix-up. Jira cannot restrict a specific field to only be editable by a particular user or group on a screen.
- Security to view this issue is only at the level in which security is applied. Super admins can still get in and see the tasks that they usually would not be able to see when not accessing it from the back admin superpowers. It is NOT 100% confidential, so limit what you create as tasks in this space.
- The act of recurring in this design is built into the act of using the swimlanes and quick filters that group things based on underlined queries. As you work; you are resetting values or status to be brought back up in a swimlane or filter to group items in lists that you can work from.
Additional Option
- This structure also works well if you create a dashboard for querying Jira issues, the same as your swimlanes and filters. It will provide you with a personal dashboard of your schedule.
- UPDATE:
- This can also be done using the Due Date field, which would bring Jira native functionality of the due date into the picture.
- A simple TODO, In Progress, and Done workflow also works fine. Using the Date field of your choice either a new custom field or the due date field. while a task is in progress, update the due date field each time you touch the tasks and change it to the date on which you want to be signaled for it to appear in your day's work list. If the task is not done and you want to be reminded of it again in two days then advance your date field by two days and let your swim lanes filter this into your list or use your dashboard to have it separated in a query-based widget.
- A reminder this is for items created in a specific task-tracking project, for other projects where additional work is created, I suggest creating a second board in your task-tracking project where the underlined query pulls in all issue types created in and outside of your task-tracking project. This concept allows for outside projects to run as normal but provides users with a single location to pick up and manage all of their work. NOTE: if you are using a custom field for your date you will want to put this on all of your screens so that it can be managed in the task tracking project effectively and not interfere with the due date field as external projects will use this to represent when that work is due vs when a user wants to recall the task in there, task tracker.
I hope these insights and steps are helpful. I'm also open to hearing other methods or improvements on this approach!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.