Content
Stock Visibility Solution
SVS Code Release Versioning
Page Comparison
View Page
Export to Word
Export to PDF
Archive
Page history
View ownership
A
t
tachments (0)
Page Information
View Source
Versions Compared
Old Version
6
changes.mady.by.user
Nyameko Mateke
Saved on
Jun 20, 2018
compared with
New Version
Current
changes.mady.by.user
Nyameko Mateke
Saved on
Jun 20, 2018
Previous Change: Difference between versions 5 and 6
View Page History
Key
This line was added.
This line was removed.
Formatting was changed.
Comment:
Import Macro Repair
Overview
SVS Bitbucket repo
JIRA Project
Release and tagging
Web upgrade
Journey upgrade
...
Info
title
JIRA Project Management
All current development work must be documented through JIRA tickets .
All tickets must reflect their target project code
Development work that involves a commenting to the Bitbucket must be committed / created / reflected on the Ticket
Each Major release version must be have been reflected in a form on an epic
on JIRA
Info
title
Managing Release upgrade
on
the DSL
All web app release must be document in a form of a
JIRA
JIRA
...
Ticket
List of all SQL Migrations Scrips where applicable
Indication of any possible effect to any middleware
The JIRA ticket must be linked as related issue / subtask / Check Box
An increment to the release version must done and be reflected from the Web App
Each Major release the whole team must be aware.
If the release involves Journey , the source code must be pulled and committed to the Bitbucket repository.
Filter by label (Content by label)
showLabels
false
max
5
spaces
ES
showSpace
false
sort
modified
reverse
true
type
page
cql
label = "sourcecontrol" and type = "page" and space = "ES"
labels
SourceControl
...
Manage space
Manage content
Integrations
{"serverDuration": 266, "requestCorrelationId": "0454a776023243f49871c0d7c315ef5b"}