Atlassian Manual
Unclassified
Atlassian Manual
Revision: 1.0
Commtact Document Number:
Creation Date: 03.11.2021
Last Update: 01.12.2024
PROPRIETARY INFORMATION
The information and ideas contained herein are proprietary to Commtact Ltd and
shall not be duplicated or disclosed outside the receiving organization or the
receiving organization's potential customer without prior written approval from
Commtact, nor used by the receiving organization or any of its subsidiaries or
affiliates, for any purpose other than evaluation of the ideas and work contained
herein.
3.Preface
3.1Abstract
This document describes the common rules to use Atlassian frameworks.
3.2Document Approvals
Signature Name Position Com
pany
Com
Leonid Prepa
VP R&D mtac
Itkin red By
t
Com Check
mtac ed By
t
Atlassian Manual
Com Appro
mtac ved
t By
Table 1: Document Approvals
3.3Revision History
Re
Description Author Date
v
Initial Version Leonid
06.02.2021 0.0
Itkin
Updated Version Leonid
01.12.2024 1.0
Itkin
2.0
Table 2: Revision History
4. Introduction
4.1Tutorials
https://support.atlassian.com/jira-software-cloud/resources/
https://support.atlassian.com/confluence-cloud/resources/
https://marketplace.atlassian.com/apps/30899/rmsis-requirements-management-
for-jira?tab=overview&hosting=cloud
https://marketplace.atlassian.com/apps/1223344/qality-plus-test-management-for-
jira?tab=overview&hosting=cloud
PAGE 1 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
4.2Full Development Flow
4.3Issue types
Description Issue Type
A problem or error. Bug
functionality or features expressed as user FR (Functional Requirements)
goals.
The detailed development/design Task
implementation task for a new feature of the
product, which has yet to be developed.
A small piece of work that's part of a larger Sub-task
task.
A collection of related bugs, and tasks. Release Content
Release Candidate check list Release candidate
PAGE 2 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
Description Issue Type
This JIRA Issue Type is used to create QAlity Quality Test
test case.
Milestone Project Milestone
4.4Statuses of the Issues
4.4.1 Milestone/Release content Flow
PAGE 3 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
4.4.2 Release Candidate Flow
4.4.3 Test Flow
PAGE 4 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
4.4.4 Bugs Flow
4.4.5 Tasks/Functional Requirements Flow
PAGE 5 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
5. Confluence
5.1Structure
5.2Insert a document
Go to import Word document
1. To start, open a blank page by selecting Create in the top navigation (or by using the next to Pages
in the sidebar). The template browser will open on the right.
2. Select the Import tab (next to Templates).
3. Decide which document type you want to import: Word document (.docx), Google Doc, or
OneDrive.
PAGE 6 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
Proceed per instructions
https://www.youtube.com/shorts/juxT-cKDgJk
Example:
https://commtactsite.atlassian.net/wiki/spaces/S/pages/4292610/SRD+Solan
5.3Insert/Create a new Jira issue
5.3.1.1 Go to relevant page on Confluence and entry the editor mode
5.3.1.2 Mark the relevant text
5.3.1.3 Choice Jira insert
5.3.1.4 Create New Issue - FR
1. Select a project from a list
2. Issue type: select from a list - FR
3. Summary filled automatically, might be updated by user
4. Add description if needed.
5. After inserting ALL required issues to type, type “Publish” to save changes.
6. Every “FR” should be related to particular release from a list
PAGE 7 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
5.4 Confluence Jira connection
6. Tasks
Above explained as System Engineer defines requirements (FR) 5.3.
While FRs are defined, the development team leader will open the Dev Task
(RF/Digital/FPGA/SW) related to specific FR.
When Dev tasks is opening required relate him as “child of” to the FR.
By end of this process, automatically created a work plan for particular release.
PAGE 8 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
7. Release creation
7.1Release definition
By default, each FR created in status “Backlog”. System Engineer together with PM
should defined the release # and time frame.
After the release definitions, click on “Backlog”
Will appear the following screen and required “drag” FRs to relevant release
PAGE 9 OF 28 PAGES REV. 1.0 DOC NO.
Atlassian Manual
By end of this mapping process created content for each release.
Release content will automatically all development tasks for different discipline, in
case of corrected definition start/stop dates, the work plan is existing.
While WP is agreed, this plan is freeze as Baseline in Gantt application.
8. Jira Applications
PAGE 10 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
9. Gantt
9.1Dependencies
9.2Tracking
On tab Task progress, simply check the checkbox “Time tracking “.
PAGE 11 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
By default, task progress is calculated as "time spent" / ("time spent" + "remaining
estimate"). This means a task becomes 100% complete if the remaining estimate is
set to zero or is not defined. A task in status Done shows percent complete less than
100% if remaining time for the task is bigger than zero. Having remaining estimate on
task means there is more work to it. We recommend having remaining estimate zero
on completed tasks, as this may cause invalid calculation of remaining work in
different reporting tools.
Use case #1. Your company doesn't set zero as remaining estimate on Done tasks, so
Done tasks are shown with progress less than 100%.
Solution: add an override for status Done and set 100 as percent value. All tasks in
status Done will have 100% regardless time spent.
Use case #2. Your company doesn't use Jira's time tracking feature to log the time
spent, or you just want to base progress value on issue status.
Solution: add overrides for multiple statuses, setting different progress value for each
of them. For example, you could set "Not started" = 0, "In Progress" = 50, "Done" =
100, etc.
Please note that overridden task progress calculation doesn't apply to parent tasks.
Parent tasks always have their progress calculated from children tasks.
To add an override, go to chart configuration and open Task progress tab. Then,
select a status and insert the required percentage. Then, click Save.
PAGE 12 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
The defined by administrator overrides will appear by default in newly created charts.
Although, each chart owner can modify or remove the overrides if needed.
Once the task progress overrides are added to the chart configuration, the values for
Time Spent and Remaining Estimate on information window for the task will be
overridden as well, considering the applied percentage.
Let’s go over an example case which involves the parent task, child task and sub-task
to see how the added task progress overrides affect the chart.
Initially, with no overrides added, the parent task has 25% progress:
Let’s assume the chart owner has added the next overrides for the statuses To Do
and In Progress that are used in this example:
PAGE 13 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
If prior to adding the overrides, the child task had 0% progress, now it has 20%
progress:
The progress for sub-task has changed from 75% to 30%, according to the overrides:
Please note that progress for the parent task wasn’t affected by the added overrides.
Even though the parent task has status In Progress, its progress is always based on
PAGE 14 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
children tasks and is calculated by the formula "time spent" / ("time spent" +
"remaining estimate").
So, as result of added overrides, the parent task progress has changed from 25% to
23%.
As mentioned before, once the overrides are added, the Time Spent and Remaining
Estimate will be shown as overridden on info window for tasks. Please take this into
account if tracking time in Jira.
Currently the progress setting is:
9.3Links configuration
Links configuration defines where to store links between Gantt chart tasks. Select
None if you don’t plan to use a particular kind of link. The minimum setup usually
requires at least End to start link.
Hierarchy link is need for child / parent relationships between arbitrary tasks.
Multiple levels of hierarchy are supported.
PAGE 15 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
Jira sub-tasks are always shown as children of their parent issue, and don’t need
Hierarchy link setup for this.
10. Sprint
10.1 Purpose
The purpose of the sprint is to create the focusing work plan per specific period.
A sprint allows focusing the development team on important issues at the project to
allow the progress.
10.2 How to
10.2.1 Open a sprint
PAGE 16 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
- Click on create sprint
- Open edit sprint
- Fill marked areas
10.2.2 Fill content
- Choice issue/issues and move to sprint
PAGE 17 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
Sprint target: to complete all issues during a sprint (move them ready for SV at
least) and be ready with clear list for the next sprint tasks.
Very important during working on any issue to open "Clockwork"
10.2.3 Following
10.2.4 Reports
PAGE 18 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
11. QAlity Plus
11.1Documentation
https://soldevelo.atlassian.net/wiki/spaces/QS/overview?
homepageId=1631322237
11.2 Main Page
11.3Test case Repository
The main idea is you have a data base of all TCs for all projects and you can associate
TC from one project to another without any cloning and duplication.
Example from one project:
PAGE 19 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
11.4Test Cycle
The term Test Cycle is the similar to particular Test Plan.
You can create the cycle for any purposes – STP/Regression/Bug verification/Sanity
and etc.
PAGE 20 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
PAGE 21 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
12. RMsis
This application allows to create and follow up the full product/release line
traceability: from customer requirements till test cases execution and bugs.
PAGE 22 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
12.1 User guide clear and simple: a lot of the
reports/analyze capabilities
12.2 Creation traceability:
- Click on related place on column
- Choice the relevant Jira issue/s
In case of no related Jira’s, directly could open a new one.
PAGE 23 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
12.3 Connection to/from Jira
PAGE 24 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
13. GIT connection
PAGE 25 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
PAGE 26 OF 28 REV. 1.0 DOC NO.
PAGES
Atlassian Manual
14.Others
14.1 Clockwork
14.2 Dashboard
PAGE 27 OF 28 REV. 1.0 DOC NO.
PAGES
