2020-10-6 SDLC Core Team Meeting
Date
Oct 6, 2020
Attendees
@Jessica Henderson
@Michael Oatley (Deactivated)
@Veronica Ferriss (Deactivated)
@Ruben Mercado
@Sherry Rodriguez (Deactivated)
@Will Harris
@Yi Zhang
@Sumanth Reddy
@Bharani Rajendran
Goals
Discuss Atlassian Application maintenance and operational support
Discussion items
Discuss best way to report SDLC application issues
Teams Atlassian Technical Team
Verify Teams are configured for notifications: Team>General>Channel Notifications
Create new smaller Core Team and pull in Atlassian Tech Team as needed? (Mike O., Jess, Veronica, Ruben, Sumanth, Bharani, Yi, Sherry and Will)
Email
Discuss need and frequency to copy Prod data to Test environment
Discuss approach & methodology: Clone or Project copy
Team member involvement, planning, configuration and scheduling (e.g. Jira and JSD admins to work with Config Mgmt)
Jira Plug-in's:
Renewals in process:
UConn Procurement had this on hold owing to questions about Carahsoft vendor. Working with Procurement to process asap, given expiration dates.
Colin McNeil (OVPR) requested bulk export of JSD issues. Discuss possible plug-in's (AIO power bi connector for Jira, eazybi, tableau)
Need for other plug-in's?
Application versions
Discuss best time to assess, plan and schedule Confluence Upgrade
SDLC roadmap requires updates. Review process and documentation.
Discuss 10/4-105 JSD problem. Tickets not automatically created via email. RE: Atlassian ticket SDS-54375 processing inbound emails status
Open Discussion
Open Items | Who | Notes |
|---|---|---|
Confluence Upgrade Version? | Yi | Yi is interested in Version 7.7 that has accessibility improvements and cluster re-indexing without downtime. |
|
|
|
Action items
Owing to Procurement issues, the following 4 plug-in's were purchased and applied to Jira on 10/13/20: Refined for Jira Service Desk, Jira Misc Custom Fields, User Profiles for Jira and Automation for Jira.
Schedule will be based on support availability, including testing.
Comments
I believe the software development template is widely used so we would want to ensure compatability.
RE: bulk export JSD issues
Colin is interested in pursuing a way to bulk export JSD issues. Mike O. and Jess discussed various options, including the possibility of development of a data warehouse or web focus report. Both options would require someone to understand the back end table structure and development time and resources. We believe the AIO power bi connector plug-in would be the best solution, as it seems to meet the need and would be more easily maintained. With UConn's Academic discount pricing, the plug-in would cost $6,500/year.
Sherry spoke with Haleh regarding Colin's request for a tool to better handle bulk JSD issue exports. Per Haleh: "I would not want to purchase. But I would like for Colin to work with someone in Rob Rowland area and come up with a better solution that he has right now. He does have a query that takes a very long time to run. He is familiar with the data structure, so I think that if he could consult with an expert, he could get a much better outcome."
Per Mike Long 10/29/20:
Set-up JIRA as an available WebFOCUS data source in the UAT environment https://webfocusluat.its.uconn.edu/ibi_apps
To get to JIRA data, navigate through the ITS folder and into the ITS Help Desk sub folder. I created two very simple samples that dump data from a jira_source table to ensure I was retrieving data, I left those there for now.
Colin may proceed with testing.
Looking at compatibility & planning out time required.
Looks like its an offline upgrade. So, has to be scheduled and downtime required.
4 of the 5 apps here have to be upgraded after confluence upgrade to 774. (impact / functionality to be tested). TBD on what functionality is changing in them & if its ok.
Universal plugin Manager is disabled. If you see a need / use later, it needs to be vetted (now or later).
Compatible and nothing to do here:
How critical are these? They are not validated just yet.
Can we test them in test / dev environments?