I'm all in favour of keeping things as simple as possible, that's why I
want to add new flag, as current behaviour is not intuitive and simple
for me ;)
Especially, that I need to ask someone to add new assignees and it makes
process more complicated - it requires two persons now. When I can't get
hold on anyone able to edit Jira users I leave assignee as myself (and
usually forget about that issue) - in result we loose some information
in Jira.
Also as a simplification I suggested removal of "Close" transition and
state.
I hope more commiters join discussion ;) (if not I'll at least try to
suggest update to doc/commitets.md as for now it does not mention
anything about assignee).
-kg
W dniu 2015-05-04 o 04:19, Jake Farrell pisze:
I feel like we have had this conversation before on the dev list...
I'm in favor of keeping things as simple for the committer as possibly,
introducing more steps or flags just leave the possibility for something to
get missed.
Currently anyone that is listed as the contributor role in our jira project
can be assigned an issue, we could open this up to be assignable by any
jira user, but in the past there was issues in other projects when this was
the default and that is why it was changed across the board. Agree that
this step of setting the assignee in jira is a little redundant since we
have it in the commit, but I like that we have that extra information to go
off from, and it makes looking through issues and tracking down problems a
little easier I think. I also like that we have that audit trail in jira to
help us look at earned merit when adding new committers.
If the current process can be improved then great, I just want to make sure
we document it and keep it as simple as possible, whatever we decide to do
as a group
-Jake
On Sun, May 3, 2015 at 3:14 PM, Konrad Grochowski <[email protected]> wrote:
Hi All,
Recent discussion in https://issues.apache.org/jira/browse/THRIFT-3105
shows that maybe we need to redesign our Jira workflow.
As for now I see couple of problems:
1. not every user can be assigned to issue. As long as we use "Assignee"
field to indicate "patch author" this makes it trouble some. I was unable
to find how to add user to "allowed assignees" in Jira, but maybe I have
wrong role in Jira project myself.
2. We loose information who did commit patch. After few months it's hard
to expect some contributor to rethink his/hers patch when some problems
appear, yet we could expect commiter to be an 'expert' in issue he worked
on (assuming it was more work than 'git apply; git commit -a; git push' ;)
).
3. We lack ability to mark issue as "Commiter is working on applying
patch".
4. "Close" state usability is unclear - who should close issue, when, what
kind of issues can be closed etc.
My suggested solution:
a. Add new field to Jira issues - Patch Author (we already have "Patch
Available" so it would be consistent) with ability to assign any Jira user
to it. This field should be required on Open -> Resolved transition screen.
b. Use Assignee field to indicate commiter who is working on applying
issue. When issue is resolved - it should point to author of commit.
c. Remove 'Closed' state as it seems to not provide any additional
information.
Just a topic to discussion :)
Best regards,
Konrad
