Filter cards by user logged on?? Is there a way to do that?
Hi All,
Context: we have one single Mingle project to handle Support tasks (defects, bugs) for different applications. Each application has its own Product Owner.
And, due to a specific requirement, we don't want a Product Owner to be able to see what are the items being worked on for another application (ie: for another Product Owner).We would like to have a tab which would be something like a "Todo" list for developers, in which we could filter all unassigned tasks so that developers can grab and start working on them.
BUT we would like to make sure that if a Product Owner goes to that tab, he/she can only see tasks for his/her project, and not other projects.So, we were thinking of doing something such as:
SELECT name WHERE Type = Task AND Project = '<some project>' AND 'Development Owner' IS null AND CURRENT USER is not '<unauthorized user>' // or CURRENT USER is not IN ('<list of unauthorized users'>)The problem is, that MQL does not allow to put CURRENT USER as part of the filter on the left hand side of a comparison. It only allows properties for that purpose.
So when we try a query such as the one above, we get an error that reads something like: "you're using a Mingle keyword as a property, maybe you should enclose it in brackets or quotes, etc. etc."
Is there a way I can accomplish this, to filter cards by the user logged on??
If anyone knows a way, please let me know.Thanks!
-
My thoughts would be to set 'Project' to be the Product owners sign in name (assuming Project isn't refering to the mingle project but the application?). Then you can test this against the CURRENT USER, such as in snippet below that shows only the stories where the current user is the BA contact
{{ table query: SELECT name,number WHERE Type =story AND 'Story Status' <'Awaiting sign off' and 'BA contact' = CURRENT USER}}
I assume that all other filters are in personal favourites, and this would be the only contentious filter in Team favourites?
The other way could be to have a separate mingle project for each application that only the Product owner logs into, and there the filters refer back to the main mingle project using the Project seetting in each query, to give an extra level of separation and flexibility
-
Thanks Ian.
Yes, the 'Project' card refers to the application and not to the Mingle project.
So we have the tree: Project > MMF > Story > Task
Regarding your query above, I guess you meant:
{{ table query: SELECT name,number WHERE Type =story AND 'Story Status' <'Awaiting sign off' and Project = CURRENT USER}}
So, "Project" and not the hardcoded "BA contact" value?
Your solution is a valid option definitely.
Thanks!
Any other thoughts anyone?
Please sign in to leave a comment.
Comments
2 comments