I think that in a community based Bugtracker, everyone can work on any
bug. A ticket is not under someone property, the assign attribute exists
to say that we intend to work on it.
There is no problem to work on an already assigned Jira, and provide
patch. Collaborating to get the best solution is the good way to do.
In my opinion, if i'm interested in a already assigned bug, i'll try too
provide a patch/start a discussion, without reassigning it to myself.
But if i pick up a jira and then consider i'm not able to to it, i'll
try to unassign myself from it.
Only if there is not answer and i got a good solution to the issue, i
can take the assignment ?
Am i wrong ?
Gil
On 22/06/2015 10:10, Sharan-F wrote:
Hi Everyone
Another topic that came up on the Community Day was whether a developer
could pick up a Jira issue already assigned to someone else.
At the moment I don't think we have any indication to show whether the
original assignee wants to keep the issue (e.g. they are already part way
through developing a solution) or whether they don't mind if someone else
picks it up to complete.
Does anyone have any feedback or ideas about how we could handle this?
Thanks
Sharan
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Picking-up-Jira-Issues-Assigned-to-Someone-Else-tp4670453.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
