nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to configure a simple "to-do project"?

Borek Bernard

I'm trying to configure a simple project that will only have tasks and three states - todo, in progress and done. I have tried to achieve that by using the built-in Task and Sub-task issue types and a custom workflow, however, there are lots of fields I'm not interested in, e.g. Component or Fix version. I'm also not sure whether it's correct to use built-in issue types Task and Sub-task or if I'd be better off creating a completely new and custom issue types. The same with states - should I use "Open" and "Closed" for "todo" and "done" or would it be better to create custom states?

Will I need to create custom screens? I've never done that so I'm not sure how difficult or easy that is.

If someone could provide a list of steps they would take to configure a simple todo-style project, it would be very welcome.

Accepted answers

Christian Czaia [Decadis AG]

Hi Borek,

I'd suggest you create everything according to your needs. It might take you a bit when you do it for the first time bet it's worth it. A clean issue type associated with a simple workflow and predefined statuses, solutions and screens are the way you should go. I've found a nice visual process that helped me in the first place. You find all the information you need here:

http://confluence.atlassian.com/display/JIRA044/Configuring+Fields+and+Screens

All comments

Borek Bernard

Hm, my "simple" workflow doesn't properly set the "resolution" field and tasks, though "closed", appear in the Outstanding filter. I'm confused as how to set the resolution after the task has been closed or how to edit the workflow now that it's used. This is quite a painful experience (ideally there should be a "project template" that would configure all these details for me).

Christian Czaia [Decadis AG]

Hi Borek,

http://confluence.atlassian.com/display/JIRA044/Configuring+Fields+and+Screens

Borek Bernard

Thanks, and would you suggest using the built-in Task and Subtask issue types or creating some custom ones?

Nic Brough -Adaptavist-

Project templates don't really help, I've found everyone goes "it's not right" and starts from scratch.

For editing the workflow now it's in use, go to the list of workflows and find it. Look for a "draft" option - that will create a copy, and you can change that. When you're happy, you can publish it. The draft-editor does have some limitations because it doesn't let you make changes that might lead to having to migrate data (deleting a step for example, means you need to look for, and update any issues currently on that step)

For setting the resolution, you can either

Put the resolution field on the "resolve" screen, if you want to have the user choose it. You may need to go back over your workflow to identify other transitions that it should be set on to make sure they have screens with the resolution on them.
Add a post-function to every resolve/close transition that will set the resolution to a fixed value (I do this a lot, when people decide they don't want to use the global resolution, I still set it in the workflow so their "closed" issues still look "closed")

For blanking it out, much the same as 2 above - use a post-function to clear the value on re-open.

For an example, have a look at the Jira default workflow that is built in. Most importantly, look at the Resolve and Re-Open transitions - you'll find a good screen on resolve and the post-function on re-open.