Tickets in branch:Update MMT to use the new EDL groups API and integrate these groups with CMR ACLs
Staff wrote tests for "Manage CMR"->subscriptions
MMT update to no longer call the CMR uberjar for any group management tasks, but rather use EDL sit environment.
MMT updated to not show error stating "Name is limited to having letter, numbers, periods and underscores" and the user should be added to the group successfully.
EDL Integration branch merged to Master branch (PI Objective completed)
11/21/2022
12/07/2022
PENDING
PI 22.4.4
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8728
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.189.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.189.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
Tickets in branch:Update MMT to use the new EDL groups API and integrate these groups with CMR ACLs
Fix EDL Tests Part 1, 2, 3, and 4.
Update EDL tests to use flag :none to reuse user permission settings.
11/7/2022
11/23/2022
12/07/2022
X
PI 22.4.3
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8727
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.188.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,status
columns
key,summary,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.188.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
Preview Gem removed from MMT
Tickets in branch:Update MMT to use the new EDL groups API and integrate these groups with CMR ACLs
Staff wrote tests for Manage CMR->Permissions and Chooser functionality
Staff wrote test for "Manage CMR"->Provider Identity Permission and Order
Staff wrote test for "Manage CMR"->Groups" system level
Staff wrote Manage CMR"->service_entries tests
10/24/2022
11/9/2022
11/23/2022
PI 22.4.2
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8726
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.187.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,status
columns
key,summary,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.187.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT nokogiri upgrade from 1.13.7 to 1.13.9
Tickets in branch:Update MMT to use the new EDL groups API and integrate these groups with CMR ACLs
Staff wrote proposal permissions tests
Staff wrote "Manage CMR"->Service Option Assignment
Staff wrote "Manage CMR" → Group tests
10/10/1022
10/26/2022
11/9/2022
PI 22.4.1
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8725
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.186.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,status
columns
key,summary,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.186.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT updated to setup ACLs in the local environment to use new bearer token instead of ECHO token.
MMT user can save a collection draft to their local machine and an option is presented to upload a collection draft to MMT.
Staff started updating "Manage CMR"->Groups code tests for new EDL groups API.
9/26/2022
10/12/2022
10/26/2022
PI 22.3.IP
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8349
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.185.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,status
columns
key,summary,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.185.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
The upper and lower sections of the MMT preview page remains aligned when the page is zoom'ed in/out
Tickets in branch:Update MMT to use the new EDL groups API and integrate these groups with CMR ACLs
Staff wrote tests for "Manage CMR"->subscriptions
MMT update to no longer call the CMR uberjar for any group management tasks, but rather use EDL sit environment.
MMT updated to not show error stating "Name is limited to having letter, numbers, periods and underscores" and the user should be added to the group successfully.
EDL Integration branch merged to Master branch (PI Objective completed)
11/21/2022
12/07/2022
PENDING
PI 22.4.4
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8728
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.189.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.189.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
Tickets in branch:Update MMT to use the new EDL groups API and integrate these groups with CMR ACLs
Fix EDL Tests Part 1, 2, 3, and 4.
Update EDL tests to use flag :none to reuse user permission settings.
11/7/2022
11/23/2022
12/07/2022
X
PI 22.4.3
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8727
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.188.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,status
columns
key,summary,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.188.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
Preview Gem removed from MMT
Tickets in branch:Update MMT to use the new EDL groups API and integrate these groups with CMR ACLs
Staff wrote tests for Manage CMR->Permissions and Chooser functionality
Staff wrote test for "Manage CMR"->Provider Identity Permission and Order
Staff wrote test for "Manage CMR"->Groups" system level
Staff wrote Manage CMR"->service_entries tests
10/24/2022
11/9/2022
11/23/2022
PI 22.4.2
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8726
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.187.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,status
columns
key,summary,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.187.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT nokogiri upgrade from 1.13.7 to 1.13.9
Tickets in branch:Update MMT to use the new EDL groups API and integrate these groups with CMR ACLs
Staff wrote proposal permissions tests
Staff wrote "Manage CMR"->Service Option Assignment
Staff wrote "Manage CMR" → Group tests
10/10/1022
10/26/2022
11/9/2022
PI 22.4.1
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8725
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.186.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,status
columns
key,summary,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.186.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT updated to setup ACLs in the local environment to use new bearer token instead of ECHO token.
MMT user can save a collection draft to their local machine and an option is presented to upload a collection draft to MMT.
Staff started updating "Manage CMR"->Groups code tests for new EDL groups API.
9/26/2022
10/12/2022
10/26/2022
PI 22.3.IP
Expand
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,issuetype,assignee,status
columns
key,summary,type,assignee,status
maximumIssues
20
jqlQuery
project=MMT AND sprint = 8349
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
MMT-1.185.0
Jira
server
Earthdata Ticketing System
columnIds
issuekey,summary,status
columns
key,summary,status
maximumIssues
20
jqlQuery
fixVersion = MMT-1.185.0
serverId
9a2ac141-7181-31f1-a247-ccbc66e20158
The upper and lower sections of the MMT preview page remains aligned when the page is zoom'ed in/out
Success: Deployment of 1.172.18 to MMT-PROD Success: Deployment of 1.172.18 to DMMT-OPS Success: Deployment of DASH-22.1.5.15 to PROD
Success: Deployment of IDN-22.1.6.14 to OPS
UAT
Success: Deployment of 1.173.12 to DMMT-UAT Success: Deployment of 1.173.12 to MMT-UAT Success: Deployment of IDN-22.1.6.14 to UAT Success: Deployment of DASH-22.1.6.12 to UAT Success: Deployment of KMS-22.1.6.4 to KMS UAT Success: Deployment of KMS-22.1.6.4 to KEYWORDMANAGER UAT
Success: Deployment of KMS-22.1.3.8 to KEYWORDMANAGER UAT
Success: Deployment of KMS-22.1.3.8 to KMS UAT
Success: Deployment of 1.170.0 to MMT-UAT
Success: Deployment of 1.170.0 to DMMT-UAT
Success: Deployment of IDN-22.1.3.14 to UAT
2/16/2022
PROD
NONE
UAT
Success: Deployment of 1.169.11 to MMT-UAT Success: Deployment of 1.169.11 to DMMT-UAT Success: Deployment of DASH-22.1.2.0 to UAT
hot fix: test roll back of location level4 keywords Success: Deployment of fix-KMS-21.4.IP.2.b-1 to KEYWORDMANAGER SIT Success: Deployment of fix-KMS-21.4.IP.2.b-1 to KMS SIT Success: Deployment of fix-KMS-21.4.IP.2.b-1 to KMS UAT Success: Deployment of fix-KMS-21.4.IP.2.b-1 to KEYWORDMANAGER UAT Success: Deployment of fix-KMS-21.4.IP.2.b-1 to KMS OPS Success: Deployment of fix-KMS-21.4.IP.2.b-1 to KEYWORDMANAGER OPS
- reset KMS SIT/UAT Success: Deployment of KMS-22.1.3.0 to KMS SIT Success: Deployment of KMS-22.1.3.0 to KEYWORDMANAGER SIT
Success: Deployment of KMS-22.1.1.1 to KMS UAT Success: Deployment of KMS-22.1.1.1 to KEYWORDMANAGER UAT
2/2/2022
(2pm)
hotfix for KMS-401 deployed to SIT/UAT/PROD, then rolled back in SIT/UAT
Success: Deployment of KMS-22.1.2.0 to KMS UAT Success: Deployment of KMS-22.1.2.0 to KEYWORDMANAGER UAT
Success: Deployment of KMS-22.1.2.0 to KMS OPS Success: Deployment of KMS-22.1.2.0 to KEYWORDMANAGER OPS
rollback hotfix Success: Deployment of KMS-22.1.1.1 to KMS SIT Success: Deployment of KMS-22.1.1.1 to KEYWORDMANAGER SIT
Success: Deployment of KMS-22.1.1.1 to KMS UAT Success: Deployment of KMS-22.1.1.1 to KEYWORDMANAGER UAT
2/2/2022
(10am)
PROD
None
UAT
MMT (depends on release of CMR-7479 & MMT-2657 to UAT)
Success: Deployment of 1.169.0 to MMT-UAT Success: Deployment of 1.169.0 to DMMT-UAT
Success: Deployment of KMS-22.1.1.2 to KMS UAT Success: Deployment of KMS-22.1.1.2 to KEYWORDMANAGER UAT
01/26/2022
PROD
Success: Deployment of DASH-21.4.IP.1.0 to PROD
Success: Deployment of KMS-21.4.IP.2.5 to KMS OPS Success: Deployment of KMS-21.4.IP.2.5 to KEYWORDMANAGER OPS
UAT
Success: Deployment of KMS-22.1.1.1 to KMS UAT Success: Deployment of KMS-22.1.1.1 to KEYWORDMANAGER UAT
01/12/2022
PROD . Success: Deployment of 1.167.3 to MMT-PROD . Success: Deployment of KMS-21.4.IP.2.2 to KMS OPS . Success: Deployment of KMS-21.4.IP.2.2 to KEYWORDMANAGER OPS
UAT
Success: Deployment of DASH-21.4.IP.1.0 to UAT
. Success: Deployment of KMS-21.4.IP.2.5 to KEYWORDMANAGER UAT . Success: Deployment of KMS-21.4.IP.2.5 to KMS UAT
01/07/2022
PROD
Success: Deployment of KMS-21.4.IP.2.2 to KEYWORDMANAGER OPS
01/06/2022
UAT
Success: Deployment of KMS-21.4.IP.2.2 to KEYWORDMANAGER UAT
12/20/2021
UAT
Success: Deployment of 1.167.3 to MMT-UAT
12/15/2021
PROD
Success: Deployment of 1.165.17 to DMMT-OPS Success: Deployment of 1.165.17 to MMT-PROD
Success: Deployment of DASH-21.4.3.1 to PROD
Success: Deployment of KMS-21.4.4.2 to KMS OPS Success: Deployment of KMS-21.4.4.2 to KEYWORDMANAGER OPS
Success: Deployment of IDN-21.4.5.4 to OPS
UAT
Success: Deployment of 1.166.11 to MMT-UAT Success: Deployment of 1.166.11 to DMMT-UAT Success: Deployment of KMS-21.4.5.5 to KMS UAT Success: Deployment of KMS-21.4.5.5 to KEYWORDMANAGER UAT
12/8/2021
PROD
Success: Deployment of 1.165.17 to MMT-PROD
12/6/2021
UAT
Success: Deployment of IDN-21.4.5.4 to UAT
12/1/2021
PROD
Success: Deployment of 1.164.10 to MMT-PROD Success: Deployment of 1.162.11 to DMMT-OPS
Success: Deployment of DASH-21.4.3.0 to PROD
Success: Deployment of KMS-21.4.3.5 to KEYWORDMANAGER OPS Success: Deployment of KMS-21.4.3.5 to KMS OPS
UAT
Success: Deployment of 1.165.17 to MMT-UAT Success: Deployment of 1.165.17 to DMMT-UAT
Success: Deployment of DASH-21.4.3.1 to UAT
Success: Deployment of KMS-21.4.4.2 to KMS UAT Success: Deployment of KMS-21.4.4.2 to KEYWORDMANAGER UAT
11/17/2021
PROD
Success: Deployment of 1.163.8 to MMT-PROD Success: Deployment of 1.162.11 to DMMT-OPS Success: Deployment of IDN-21.4.2.4 to OPS
UAT
Success: Deployment of KMS-21.4.3.5 to KMS UAT Success: Deployment of DASH-21.4.3.0 to UAT Success: Deployment of 1.164.10 to MMT-UAT
11/3/2020
PROD
Success: Deployment of 1.162.11 to MMT-PROD
UAT
Success: Deployment of 1.163.8 to MMT-UAT
Success: Deployment of DASH-21.4.2.0 to UAT
Success: Deployment of IDN-21.4.2.4 to UAT
PROD
Success: Deployment of GKV-21.3.IP.1 to OPS
Success: Deployment of 1.161.9 to MMT-PROD Success: Deployment of 1.161.9 to DMMT-OPS
UAT
Success: Deployment of 1.162.11 to DMMT-UAT Success: Deployment of 1.162.11 to MMT-UAT
10/7/2021
UAT
Success: Deployment of 1.161.9 to MMT-UAT Success: Deployment of 1.161.9 to DMMT-UAT
10/6/2021
PROD
Success: Deployment of 1.160.15 to MMT-PROD Success: Deployment of 1.160.15 to DMMT-OPS
Success: Deployment of DASH-21.3.5.3 to PROD
UAT
Success: Deployment of GKV-21.3.IP.1 to UAT
9/22/2021
PROD
Success: Deployment of 1.159.19 to MMT-PROD Success: Deployment of 1.159.19 to DMMT-OPS Success: Deployment of IDN-21.3.4.0 to OPS
UAT
Success: Deployment of 1.160.15 to MMT-UAT Success: Deployment of 1.160.15 to DMMT-UAT Success: Deployment of DASH-21.3.5.3 to UAT
9/9/2021
PROD
Success: Deployment of DASH-21.3.4.0 to PROD
Reason: Dependent on external team to deploy puppet code. (Srini)
9/8/2021
PROD
Success: Deployment of 1.158.5 to MMT-PROD Success: Deployment of 1.158.3 to DMMT-OPS
Success: Deployment of KMS-21.3.4.0 to KMS OPS Success: Deployment of KMS-21.3.4.0 to KEYWORDMANAGER OPS
UAT
Success: Deployment of 1.159.19 to MMT-UAT Success: Deployment of 1.159.19 to DMMT-UAT
Success: Deployment of IDN-21.3.4.0 to UAT
9/2/2021
UAT
Deployment of DASH-21.3.4.0 to UAT
9/1/2021
UAT
DASH-21.3.3.2 to UAT
Reason for delay: CMR-DASH release will be run manually by CI/CD (Venku) and MDT SCRUM Master (Chris). Update to UAT machines with python3 changes needed.
8/27/2021
UAT
Success: Deployment of KMS-21.3.4.0 to KMS UAT
Success: Deployment of KMS-21.3.4.0 to KEYWORDMANAGER UAT
8/25/2021
PROD
Success: Deployment of 1.158.0 to MMT-PROD Success: Deployment of 1.158.0 to DMMT-OPS
Success: Deployment of DASH-21.3.2.0 to PROD
UAT
MMT
Success: Deployment of KMS-21.3.2.1 to KMS UAT
8/12/2021
UAT
Success: Deployment of 1.158.0 to MMT-UAT
Success: Deployment of 1.158.0 to DMMT-UAT
8/11/2021
PROD
Success: Deployment of KMS-21.3.1.4 to KMS OPS
Success: Deployment of KMS-21.3.1.4 to KEYWORDMANAGER OPS
Success: Deployment of DASH-21.3.1.0 to PROD
Success: Deployment of 1.156.25 to MMT-PROD
Success: Deployment of 1.156.11 to DMMT-OPS
UAT
Success: Deployment of DASH-21.3.2.0 to UAT
7/28/2021
PROD
Success: Deployment of IDN-21.2.IP.0 to OPS
Success: Deployment of DASH-21.2.IP.0 to PROD
Success: Deployment of 1.156.0 to MMT-PROD
Success: Deployment of 1.156.0 to DMMT-OPS
UAT
MMT
Success: Deployment of KMS-21.3.1.4 to KEYWORDMANAGER UAT
Success: Deployment of KMS-21.3.1.4 to KMS UAT
Success: Deployment of DASH-21.3.1.0 to UAT
Success: Deployment of 1.156.11 to DMMT-UAT
Success: Deployment of 1.156.25 to MMT-UAT
7/19/2021
UAT
Success: Deployment of DASH-21.2.IP.0 to UAT
7/14/2021
PROD
Success: Deployment of 1.155.6 to MMT-PROD
Success: Deployment of 1.155.5 to DMMT-OPS
UAT
Success: Deployment of 1.156.0 to MMT-UAT
Success: Deployment of 1.156.0 to DMMT-UAT
Success: Deployment of IDN-21.2.IP.0 to UAT
7/2/2021
UAT
Success: Deployment of 1.155.5 to DMMT-UAT
Success: Deployment of 1.155.6 to MMT-UAT
6/30/2021
PROD
Success: Deployment of KMS-21.2.4.0 to KEYWORDMANAGER OPS
Success: Deployment of KMS-21.2.4.0 to KMS OPS
UAT
Success: Deployment of 1.155.3 to DMMT-UAT
Success: Deployment of 1.155.4 to MMT-UAT
6/16/2021
PROD
Success: Deployment of KMS-21.2.3.4 to KEYWORDMANAGER OPS
Success: Deployment of KMS-21.2.3.4 to KMS OPS
Success: Deployment of 1.153.0 to MMT-PROD
Success: Deployment of 1.153.0 to DMMT-OPS
UAT
Success: Deployment of KMS-21.2.4.0 to KEYWORDMANAGER UAT
Success: Deployment of KMS-21.2.4.0 to KMS UAT
Success: Deployment of 1.154.2 to MMT-UAT
Success: Deployment of 1.154.2 to DMMT-UAT
6/3/2021
PROD
Success: Deployment of IDN-21.2.4.0 to OPS
UAT
Success: Deployment of IDN-21.2.4.0 to UAT
6/2/2021
PROD
Success: Deployment of 1.151.4 to MMT-PROD
Success: Deployment of 1.151.4 to DMMT-OPS
Success: Deployment of KMS-21.2.2.5 to KMS OPS
Success: Deployment of KMS-21.2.2.5 to KEYWORDMANAGER OPS
UAT
Success: Deployment of KMS-21.2.3.4 to KMS UAT
Success: Deployment of KMS-21.2.3.4 to KEYWORDMANAGER UAT
Success: Deployment of 1.153.0 to DMMT-UAT
Success: Deployment of 1.153.0 to MMT-UAT
5/19/2021
UVG Success: Deployment of 21.2.1_1.7.0-b0 to OPS MMT Success: Deployment of 1.150.1 to MMT-PROD DMMT Success: Deployment of 1.150.1 to DMMT-OPS DMMT Success: Deployment of 1.151.4 to DMMT-UAT MMT Success: Deployment of 1.151.4 to MMT-UAT
CMR-DASH Success: Deployment of DASH-21.2.1.0 to PROD
KMS Success: Deployment of KMS-21.2.2.5 to KMS UAT Keyword Manager Success: Deployment of KMS-21.2.2.5 to KEYWORDMANAGER UAT
5/6/2021
KMSSuccess: Deployment of KMS-21.2.2.1 to KMS OPS (BUG FIXES)
Keyword ManagerSuccess: Deployment of KMS-21.2.2.1 to KEYWORDMANAGER OPS (BUG FIXES)
5/5/2021
UVG Success: Deployment of 21.2.1_1.7.0-b0 to UAT
MMT Success: Deployment of 1.149.2 on MMT-PROD
DMMT Success: Deployment of 1.149.2 to DMMT-OPS
DMMT Success: Deployment of 1.150.1 to DMMT-UAT
MMT Success: Deployment of 1.150.1 to MMT-UAT
CMR-DASH Success: Deployment of DASH-21.2.1.0 to UAT
CMR-DASH Success: Deployment of DASH-21.1.5.3 to PROD
IDN Success: Deployment of IDN-21.1.4.1 to OPS
KMS Success: Deployment of KMS-21.1.5.22 to KMS UAT
KMS PROD - PENDING because we had issues deploying build that was already deleted in bamboo. Contacting CI/CD team to change KMS settings in Bamboo.
KMS Success: Deployment of KMS-21.2.2.1 to KEYWORDMANAGER UAT and to KMS UAT (BUG FIXES)