JIRA project doesn't exist or you don't have permission to view it when reordering issues

[Ellen Beentjes]

I insert a JIRA filter list view and can see all the issues. 

However if I click on one of the column headers to re-order the data I get the above error message.

JIRA project doesn't exist or you don't have permission to view it.

Does anyone know why this is happening and how I can solve this?

[Nic Brough -Adaptavist- · Accepted solution]

No, because you have just about described one of the main use cases for sub tasks. What's the reason behind not wanting to use them when they do what you need?

[Jack O'Hara]

A sub task requires that it goes through the workflow that is defined for the project. I want something I can just tick off and assign a worked hours value against it.

If there really is nothing that can do this then I'll use sub tasks and possible introduce some logic to the workflow whereby if <custom_field> = 'Yes', don't follow the normal workflow.

Sub tasks also skew the 'Issues Raised vs Issues Closed' statistic at the project overview. I know I can make new filters for this statistic to exclude sub tasks, or those with the <custom_field> = 'Yes' but I also need to make my management use the same filters.

[Nic Brough -Adaptavist-]

Ah, I see, you don't want the workflow element at all.

Easiest option there is probably to have a new sub-task type, with a workflow of "open" and "done". It'll still skew your raised vs closed, but you could even set resolution as you create it so you have an automatic raised and closed at the same time counter.

[Jack O'Hara]

Accepted as answer for the previous comment. I hadn't thought of separate workflows for individual issue types. This solves the majority of my reservations about using Sub Tasks.

Thanks for your help.