We created a custom sub-task issue type called approval. Then we created a process that creates this sub-task type which is then assigned to a user. The user however cannot see these specific items under the 'Assigned to me' within the your work area. They also do not appear in the results of the default 'My open issues' filter. I also tried to create a filter just for these sub-task types but that doesn't work. I have dug pretty deeply into the documentation and didn't find anything either.
interesting. so if you create that custom sub-task manually does it show up? have you checked the behavior against the default sub-task issuetype? i just did a quick test w/ default sub-task manually and it worked ok. I may try the automation approach.
I just tried automation and it worked for me fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I did create the approval sub task manually on a story. I see it in the story view, in the worked on view but not the assigned to me view. When I create a default sub-task manually it behaves as expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the issue, once assigned to a user should indeed show in the assigned to me tab. please ensure that after they assign the issue they reload the Your work page.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have reloaded the page and they still aren't appearing. I've logged out and back in. One of them was assigned to me 3 hours ago and one was assigned yesterday. None of them are appearing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There’s something missing here or either there is a bug. It is working fine for me in my instance. If an issue is definitively assigned to you then you should see it in your work assigned to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So how do we figure out if it's something we missed or a bug? The approval sub-task is assigned to me and has been since yesterday. It still is not visible in 'you work' or 'my open issues' default filter.
Here is the default My own issues filter and when I try to add 'Approval' - I go from 2 results to 0.
Here is a custom filter I made which shows all issues assigned to me and then just a shot of the actual issue confirming that it is specifically assigned to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
so to determine if a bug you would need to work w/ Atlassian Support. However, TBH my bet is not on it being a bug. I could certainly be wrong here. The one thing I note from your images, and I'm trying to follow you here, is that the first images use Resolution = unresolved whereas the later one does not. Is it possible that this is impacting results vs. expectations?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Christine Schutta -- Welcome to the Atlassian Community!
Did you confirm that the sub-tasks are actually assigned to a person, rather than created and unassigned?
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They are created and left unassigned. The list of users who approve can be different for each issue so we are doing this assignment manually.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! As Jack noted, once they are assigned they will appear with Assigned to Me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is rather an interesting one. The search for "assigned to me" and "my open issues" are very simple and really do look just at the assignee.
It sounds like the issues are not being indexed as they are created. But my problem there is that Automation and other scripting tools that can create issues, especially the big name ones, would not neglect the issue indexing (in fact, most of them use the internal create process which indexing always happens in). The Automation rule I've just tried for sub-tasks creates issues which show up fine in my filters.
So, one very quick test - could you try re-assigning one of these non-showing issues, then re-assign it again back to the person it should be assigned to. Does that make the reporting work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have tried that and I'm still not able to see it. When the approval sub-task is created it isn't assigned by automation, it is assigned manually by a user. I will update the automation to assign it to a user and see if it is then visible in that user's your work area.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>When the approval sub-task is created it isn't assigned by automation, it is assigned manually by a user
Ok, that might explain it - if an issue is not assigned, it can't be in anyone's "assigned to me" list. The issues will appear after they have been assigned to people.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They are assigned and still not appearing in 'your work' area. I've confirmed that they are also included in the default issue type scheme as well. I am able to get them to appear in a filter result but now I have to write filters for all my users so that they can see these items instead of leveraging 'your work'. Is it possible there is a bug for custom sub-tasks not appearing in the 'your work' area or the default 'my open issues' filter?
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.