Page History

...

1. Announcements:
2. Pop-up/Other Topics:
   1. Slack Questions
      1. https://fedora-project.slack.com/archives/C8B5TSR4J/p1711558664660589 - rehashing Fedora ID's to replicate object ID's in S3 (I think this was answered, but I think Emily was thinking a documentation update to include what Scott suggested would be helpful)
      2. https://fedora-project.slack.com/archives/C8B5TSR4J/p1711995943026199 - Doron's question about how to find out what's already in an index (again, I think this is resolved, but is there any follow up needed on this?)
      3. https://fedora-project.slack.com/archives/C8B5TSR4J/p1712220464339919 - Tom's questions....resolved?
   2. Use Jira filters to get ticket lists for agenda? Thomas Bernhart 
   3. Permissions to share Jira ticket filters with other users and publicly Thomas Bernhart 
3. Migration Updates:

4. Updates on:
   

   1. Open Tickets (but assigned in some cases): 
      

      Jira
      server Fedora JIRA columnIds issuekey,summary,issuetype,assignee,reporter,priority,status,created,updated columns key,summary,type,assignee,reporter,priority,status,created,updated maximumIssues 20 jqlQuery filter=10022 serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4

      
      
      

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3929

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3928

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3932

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3931

   2.  In Progress and older but still relevant open tickets:
       

      Jira
      server Fedora JIRA columnIds issuekey,summary,issuetype,assignee,reporter,priority,status,created,updated columns key,summary,type,assignee,reporter,priority,status,created,updated maximumIssues 20 jqlQuery filter=10023 serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4

      
      
      

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3918

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3927

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3923

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3924

      5. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3922

      6. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3573

   3. In Review:
      

      Jira
      server Fedora JIRA columnIds issuekey,summary,issuetype,assignee,reporter,priority,status,created,updated columns key,summary,type,assignee,reporter,priority,status,created,updated maximumIssues 20 jqlQuery filter=10024 serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4

      
      
      

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3919

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3917

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3912

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3897

      5. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3834

5. Backlog Tickets to consider working:
6. Next Meeting Chair: 
   1. Chair: Dan Field 
   2. Note Taker: James Alexander 
      

...