So I have tried to add the resolution field to the edit screen but it still shows up on the create screen. A resolution should only exist if someone is trying to close a bug. Not a task or a sub-task and definitely not on a create task/sub-task
That sounds correct. If you use "assignee = X", it looks for issues that currently have that person as the assignee.
If there are definitely issues with them as the assignee, then check the rest of your query to see if they are excluded for another reason (searching the wrong project, issuetype, custom field etc). If you still have an issue, then it might be a damaged index, but I would post your actual JQL here first to see if we can spot anything wrong with it.
project = PI AND issuetype in subTaskIssueTypes() AND assignee in (DPeregrina)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The tickets with user's assigned that won't pull in when queried also aren't allowed certain transitions if the transition has a condition of "only assign is allowed to transition".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, that's a nice clear query and a new symptom that could tell us a lot more. Now, we need to find an issue that *should* appear (assignee currently DPeregrina, and it's a subtask in PI) and look at all the user fields on it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.