Thursday, 2021-09-16

Remote meeting by Zoom, 13:00-13:15, being a part of Pääkäyttäjäverkoston kokoukset (so the Zoom link is the same) 

Agenda:

Koha Developers+Customers meetings frequency:

  • Proposed: once per 2 or 4 weeks, depending on the situation.
  • Andrii expects that we will need to have a rare separate 1h meeting, for example for some training or workshops: we agree on that beforehand.

JIRA

  1. Here is it, our project: https://jira.kansalliskirjasto.fi/browse/KOHA 
  2. Why JIRA? Some intro was in Slack #koha-asiantuntijat-ext channel
  3. JIRA access for our customers was granted. All our customers' representatives added to JIRA, as in this list: Group "koha-customers": our Koha customers JIRA group.
  4. Handy filters, more will be created:
    1. All KOHA issues (filter 23210)
    2. KOHA Publicly visible issues (filter 23211)

Now tasks ongoing, and now in comfortable JIRA-defined way:

  1. Koha 2021'Autumn version update
    KOHA-44 - Getting issue details... STATUS

  2. HeTu duplicates
    KOHA-38 - Getting issue details... STATUS

  3. Lastborrowerdate fixes
    KOHA-37 - Getting issue details... STATUS

  4. KOHA-36 - Getting issue details... STATUS  and particular one for Fikka:
    KOHA-39 - Getting issue details... STATUS

  5. KOHA-21 - Getting issue details... STATUS

  6. KOHA-22 - Getting issue details... STATUS  + parent:
    KOHA-23 - Getting issue details... STATUS

  7. KOHA-27 - Getting issue details... STATUS  + parent:
    KOHA-32 - Getting issue details... STATUS

  8.  this done:
    KOHA-33 - Getting issue details... STATUS

  9. is anyone needs that plugin (PendingReservesV2)? It will stop in new build, so needs to be updated by us:
    KOHA-35 - Getting issue details... STATUS

Minutes:

Please feel free to collaborate and note here at the time of the meeting:

  1. Transfer of existing task lists to Jira. Good to check for duplicates but they can be solved later, too.
    The important thing to remember is to leave the trace (link to KOHA-XXX) on the place from where the information token to the new ticket, so future visitors will have a link to the ticket and won't get lost. This also will be if some idea is placed in different places but will lead to the same ticket: that's useful!

  2. Security: Admins can change security (visibility) levels. By default, issues are seen by a small KK team only, so that sensitive information is not accidentally exposed. Admins can open them for a larger group of developers, including Finna; Koha customers (superlibrarians); or even more public.
    Also by default ticket is not visible to the whole KohaCustomers group but only to the reporter. JIRA/Koha team will in most cases convert those tickets to be visible by whole "Koha customers" group.
  3. General memo about JIRA usage, tools, and tricks to be placed by Andrii in Kiwi these days. Covering:
    1. Related wiki pages: 
    2. Mobile application
    3. You can create alerts: become the watcher to any tickets in KOHA- project. 

Next meeting:

  • in 2 weeks, Thursday




  • No labels