Hi Michael,
I think the issue is (using my most recent experience with
SimpleLabEntry as an example):
1. I could check out the module code, reproduce the error, commit a fix
back to trunk of the module
2. I could create a ticket to report this particular issue
3. I could _not_ mark this ticket as "Ready For Work", "Claim Issue", or
"Assign Issue". That seems restricted.
4. Because of 3, I could also not perform "Committed Code" on the issue
Thanks,
Mike
On 11/10/2011 02:41 PM, Michael Downey wrote:
On Thursday, November 10, 2011 at 2:35 PM, Michael Seaton wrote:
Right now I can commit code against module A, but I am not allowed to
create a ticket _and_ indicate within that ticket that I have
committed code unless I am specifically authorized to do so by that
JIRA project's owner.
For any JIRA project using the standard OpenMRS Workflow, the assignee
of any issue should be able to indicate code has been committed and
start a post-commit code review. If you know of specific cases where
that hasn't been possible, please let us know so we can figure out why
that's not the case.
Michael
------------------------------------------------------------------------
Click here to unsubscribe
<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l>
from OpenMRS Developers' mailing list
_________________________________________
To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
[email protected] with "SIGNOFF openmrs-devel-l" in the body (not
the subject) of your e-mail.
[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
