Design Forum 2020-08-03: The first Jira Ninjas session!

[grace (Grace Potma)]

Do you ever look at the OMRS issue management system, and feel like:

You’re not alone. This Monday, we’ll continue to do something about it!

In last week’s Jira & Issues Process Design Forum call, we agreed that we need:

1. A backlog we can start to use
2. A consistent way of addressing our backlog
3. A friendlier Jira - easier for community members to keep up-to-date
4. A process that helps Pull Requests that get reviewed
5. A process that makes it easier to track what’s going out with a platform or ref app release

Notes: Etherpad

Agenda:

• Forensic analysis update: Improving the OMRS Issue Experience: Jira Analysis 2020 - Google Slides
• Look at what the bulk rules proposed here would do / look at some examples together
• Agree on some rules to follow and next steps

When: 9:30pm IST | 7pm Nairobi | 6pm Cape Town | 4pm UTC | 12pm Boston | 9am Seattle

Where: Launch Meeting - Zoom

FYI @dkayiwa @ibacher @burke @mseaton @bistenes @herbert24 @cintiadr - please tag others you know might be interested in this topic

[grace (Grace Potma)]

FYI @dkayiwa @ibacher @gcliff I’ve updated the TRUNK and RA workflows so they are back the way they were before (due to the confusion inadvertently created at the moment by trying to remove workflow requirements), until we get the new workflow ideas sorted out together and provide more community training/awareness etc.

So e.g. it was looking like this over the weekend:

Now should look like this:

[gcliff (CLIFF GITA)]

thanks @grace for fixing this

[sharif (Sharif Magembe)]

Thanks for the fix @grace though the first workflow seems to be more vibrant with adequate workflows