[FOLIO-1191] Possible renaming of SIG labels in Jira Created: 11/Apr/18 Updated: 12/Nov/18 Resolved: 12/Apr/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Peter Murray | Assignee: | Peter Murray |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 15 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
Cate Boerema: I'm setting up a Jira workflow for the new APPIDEAS project so that labels are assigned to issues when the state is set to "In SIG Review". I noticed that your UXPROD project is using labels such as 'usermangement' and 'metadatamanagement'. What I'd like to do is set up a validator in the workflow so when an issue transitions to the "In SIG Review" state, the workflow engine will ensure that a SIG's label is assigned. I'm planning on doing this with a Regular Expression Check Validator...with the regular expression check being `/sig-*/`. Question: is your use of labels – creating a filter for SIGs to review – the same as mine? If so, would you mind transitioning to using the `sig-` labels so we don't create extraneous labels in Jira? Or other thoughts on how we could achieve the same goal? |
| Comments |
| Comment by Cate Boerema (Inactive) [ 11/Apr/18 ] |
|
I have been creating labels so I can get filters for UXPROD (for example for this view: https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=32&projectKey=UXPROD). This isn't really specifically for the SIGs to review, but for anyone (esp the POs) to quickly see the backlog of work (primarily epics and features) for a given area. There were some other sig tags created early on which I have used to tag user stories and bugs that come out of demos to the SIGs. This is so we can show the SIG we are capturing their feedback and so they can track progress on these things. For example: https://folio-org.atlassian.net/issues/?filter=10418 I haven't been tagging every user story with a SIG tag, as I haven't seen a need for it. Nearly every user story begins it's life with a SIG conversation so the lists would just be too large to be meaningful. I think your plan for labels should not conflict with mine as long as you are using a different issues type (something other than epic, feature and story)... Happy to discuss on the phone if you want. |
| Comment by Peter Murray [ 12/Apr/18 ] |
|
As we talked about on the call, it doesn't seem to make sense to combine our usages of labels right now. If we find they are unnecessary, we can combine them in the future. |