New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[6.4.x] RHBPMS-4184,JBPM-5277 - getTasksAssignedAsPotentialOwner doesn't allow groups searching, only actorid #560
Conversation
@@ -0,0 +1,50 @@ | |||
/* | |||
* Copyright 2015 Red Hat, Inc. and/or its affiliates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2016
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, thanks.
59b23b3
to
d687f1e
Compare
t.archived = 0 and | ||
potOwners.id in (:groupIds) and | ||
TYPE(potOwners) = 'Group' | ||
order by t.id DESC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor thing, but the lines in the from
and where
blocks should be indented for better readability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bikeshed! 🚲
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. Last Jira, so what the heck?
d687f1e
to
b94f406
Compare
…w groups searching, only actorid
b94f406
to
7d04f13
Compare
public void claimNextAvailable(String userId, List<String> groupIds) { | ||
executor.execute(new ClaimNextAvailableTaskCommand(userId)); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@psiroky See above (re: claim
and claimNextAvailable
)
Map<String, Object> params = new HashMap<String, Object>(); | ||
params.put("groupIds", groupIds); | ||
return (List<TaskSummary>) persistenceContext.queryWithParametersInTransaction( | ||
"TasksByPotentialOwnerGroups", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly another bikeshed, but to be consistent with the naming in the other classes, should we use different name for the query, e.g. TasksByGroups
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uhm.. If you insist on it, I'm happy to change it.
However, "TasksByPotentialOwnerGroups" describes exactly what the query does -- whereas "TasksByGroups" implies that the query is something else than what it is! For that reason, I'd like to keep the name to what it is, "TasksByPotentialOwnerGroups".
The operation name (getTasksByGroup
) was decided by @krisv -- if you think it should be called something else, please talk to him.
@mbiarnes This PR needs to be merged for the release. Thanks! |
+1 |
Related to the release this week.
PR Set: