Manage non development tasks that are not associated with any project

[Abhishek Sharma]

We usually have tasks which are not associated with any project and non development related. For example:

• Doing some modification on production server
• Modifications/update in DB server
• Writing some SQL queries
• Gather requirements from different department.

I have 3 projects in JIRA and all are associated with particular Web Apps. I want to plan such non development activities also in a Sprint but without association with a project it doesn't seem possible and adding such tasks in existing projects doesn't look like a good idea.

Should I create an entirely new project to manage only such tasks or there are some  other alternatives also?

[Nic Brough -Adaptavist-]

You do need to put them in a project, as issues cannot exist outside them.

But you could have a new project for them, or scatter them into more appropriate projects.  For example, if you have a project for "database stuff for the DBA team", you might create issues in there.

You can then come up with a way to get them included in your sprint.  A really simple option is to change the board query from "project = xxx" to "project =xxx or label = non-project", and stick a "non-project" label on the issue in the DBA project!

[Jack Brickey]

agree. I created a PIT (projects for IT) where I collect non-project specific tasks and projects.