Burke has quite reasonably brought up the point that design discussions belong on the Wiki or on this board or in design calls with conclusions being brought to the Jira ticket. (see https://wiki.openmrs.org/display/docs/Tickets#Ticket-Related_Conventions<https://wiki.openmrs.org/display/docs/Tickets#Ticket-Rleated>) However, the links between the Wiki and Jira are fragile, especially given that clusters of Wiki pages and Jira feature requests result in clusters of workable tickets. Given that the work actually occurs off of tickets, perhaps by someone who has not participated in the design discussions, only those comments on the ticket actually get considered when the work is done. Or to put it another way, it is a weakness of our process that important discussions can end up in a sidetrack, in the Wiki or on this board or in Jira, while the work goes on against another ticket.
Is there some way we could improve this process for issues that require design? For example, by saying that each Jira ticket must be either a sub-issue of another Jira ticket or of a Wiki page? The master Wiki page and Jira ticket would cross-reference all related Wiki pages and Jira tickets. Do we need to have separate design-phase and build-phase tickets? We also need a way to move back to design after tickets have been worked -- this is the case with the current discussion of object attributes, global properties and complex objects, which have turned out to be similar enough to make harmonization worthwhile. And it would be good if we could equal the convenience of watching just one ticket as opposed to multiple tickets and wiki pages. Where is the state diagram for the Jira process? _________________________________________ 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]
