Hey everyone! I’m working on setting up a JIRA project for our team to handle regular tasks like renewing software licenses, checking SSL certificates, and doing yearly database stuff. It’s called ‘Periodic Tasks.’
I’ve got the basics down. Made a new project, set up the key and description, and picked a project lead. I also created a custom issue type scheme with just ‘task’ and ‘sub-task.’ Plus, I made a notification scheme that’s currently the same as our default one.
Now I’m stuck on how to set up components. Should I organize them by the things we manage (like servers, certificates, licenses) or by the type of task (renewals, checks, processes)? Right now, I’m leaning towards task types.
Has anyone done something like this before? I’d love to hear about your setup, especially your workflow. What custom fields or screens did you find helpful? Any advice would be awesome!
I’ve managed a similar project for my team, and here’s what worked well for us:
We decided to organize components by task types (renewals, checks, processes) as it made it easier to track and report on different activities. For workflow, we kept it simple: To Do, In Progress, Review, and Done. This allowed for a quick quality check before closing tasks.
Custom fields were a game-changer. We added ‘Next Due Date’ and ‘Frequency’ fields. This helped in planning and allowed us to use Jira’s automation to create the next instance of a task once it was completed.
One thing that really helped was setting up a dashboard with JQL queries to show upcoming tasks for the next 30, 60, and 90 days. This gave us a clear view of what’s coming up.
Also, consider using the ‘Tempo Planner’ add-on if you have it. It was great for visualizing recurring tasks across a timeline.
Hope this helps! Let me know if you need any more specifics on our setup.
hey, i tried a similar setup. i found that using task types as components really streamlined things. keeping the workflow simple with todo, in progress, and done worked well. adding custom fields for due dates helped, too. give jira automation a try if you haven’t!
I’ve used JIRA for recurring tasks before, and here’s what worked well:
Organize components by task type (renewals, checks, etc.) for easier reporting. Keep the workflow simple - maybe just ‘To Do’, ‘In Progress’, and ‘Done’.
Custom fields are key. Add ‘Next Due Date’ and ‘Frequency’ fields. These let you use JIRA’s built-in automation to create the next task instance automatically when one is completed.
Set up a dashboard with JQL queries showing upcoming tasks for the next 30/60/90 days. This gives a clear overview of what’s coming up.
For automation, use JIRA’s native features rather than third-party apps initially. You can always add those later if needed.