Page History

The requirement to be done: The Jira project is created in TDS Portal as SaaS Service.

Congratulation - you are now Jira project admin. And because you are not experienced with Jira, you are here on this page. Don'

t

t be afraid of playing with your projects - you cannot damage other's work (Jira ask you if you really want to delete something) specially if the project is still empty, and we fix it anyway.

Read the manually manual to the end. In case of any question, please contact TDS Support - we are here for you!

As project administrator, you have access to the Project administration page. As admin:

You can set Components, Versions and Roles
You have to know how Permissions and Issue security works
You have to know how Issuetypes affect Issue types affect workflow and screen setting
If your project doesn't share schemes with other projects, you can partially set workflows and screens
The rest in list is not important now and/or can be set by Jira admins (TDS team).

Project board is the place where you will work at most.

Any user can create a board, not only projects admins
You can create a board in top menu Boards → View all boards → Create board

But now, create a first issue.

If you go through this page you will be able to manage your project. For further studies visitOfficial Documentation or ask directly TDS Team.

Project
settingYou can manage it or is important to know
settings
It is place where you configurate your project. Go to your project and click Project settings in main Menu( in the left bottom corner)
Expand
title Details

Section

Column
width 50%
Details
Here are the basic information of projects, names generally.
Name - Human readable name of the project. Can be changed.
Key - unique identificator of the project. When we are asking for project, give us the key or link directly. Can be changed and even existing links are not
lost
lost

If you need to change the project key , please contact TDS Support - we are here for you!

Column
width 50%

Expand
title Issutypes

Section

Column
width 30%
Issue types
You can have different types of things by using differentissue types. Also, you can configure each issue type to act differently, e.g. to follow a different process flow or track different pieces of information.
As the default you get the issue schema according to project type selection (you select it in TDS Portal during Jira project creation).
The project type selection you can check here.
Issutypes
Issutypes defines what the issue is. Each Issuetype can have separate workflow or screens.
There are many Issutypes like Bug, Task, New Feature, Change, Request, ... … Important is not the name, but the way you work with that (defined by workflows and screens)
Epic - Are used as aggregation issues. Other issutyeps can be connected with epic via "Epic link" field.
Subtask - Subtasks are special type of issutypes which must have parent task. Generally, subtasks are used when your parent has a task includes many simple "subtask" and you want to track them.
To add or edit the issue types , please contact TDS Support - we are here for you!

Column
width 50%

Expand
title Workflows

Section

Column
width 50%
A workflow describe the process of your work that an issue will follow, e.g. Open, In Progress, Resolved. You can configure how issues will transition between statuses, e.g. who can transition them, under what conditions, and which screen will be displayed for each transition.
The workflow needs to be understood by project users. It is good to keep it as simple as possible
Workflows are one of the most important "feature" of Jira.
The good workflow is the one, which when you show it to newcomer, he understands your work process immediately. Simple workflow is better than complex.
Each issuetype can have own workflow and also each project can have own set of workflows. But workflows schemes can be shared across the projects.If you want to
To use other workflow than the default
one
, please contact
TDS Team. They
TDS Support - we are here for you! They can add any statuses you want and they can add
postfunction
post functions - automation rules executing during the transition (auto-assigment, clearing of field) or validators - checking values of issues during transitions (mandatory fields, user rights).

Column
width 50%

Expand
title Screens

Section

Panel
title comment
to much info- rather to split info about Screens and Fields

Column
width 50%
Screens are the list of fields which are used on you issues.
Jira admins can create o new fields.
Each issuetype can have own screens and also each project can have own set of screens. But screen schemes can be shared across the projects.
Each issuetype have By default your project has the same Create, Edit and View screen. Can be the same or different.Workflow transition can also have screens (you can set field values during the transition).If the screen is not shared with other projects, project admin can add existing fields on screen..
Fields can be separated into tabs within the screen. Very useful for huge amount of fields.
Before you add Be careful with adding some field to the screen: wait for a while and think - how will be the field used? For example we will introduce a new field "Reopen" where we note if the issue was reopened. Users will mark issues as reopen, project owner will make analysis of reopen fields and also some action need to be done to reduce of reopened fields. If any of this this steps is missing, the field is useless. You can ask Jira admins to

To create a new field
. You have to give us name and type (number, select list, text single line, text multiple line, date, user picker, ...). Note the step above. There are many fields which were created and never used. Every new field have a performance impact.
or update screen, please contact TDS Support - we are here for you!

Column
width 50%

Expand
title Versions

Section

Column
width 50%
You can set here values for
Issues can be group in system field Versions
In Jira issue, you can find versions as Affected version (where you find the bug) and Fix Version (where you fix the bug)
You can mark versions as released

Column
width 50%

Expand
title Components

Section

Column
width 50%
Components allows you to categorize issue within the project.
Project admin can define the new components.
Components can be set with default assignee - which can speed up ticket resolution

Column
width 50%

Expand
title Users and Roles

Section

Column
width 50%
Users and Roles
First go and read Permission section
Project owner - responsible person, have to decide how the project (workflows, issutypes) should look like
You can add a user or whole group to role
Don't
do
manage users it here!

User management is solved via TDS Portal. In most cases, you shouldn't edit this page at all. Look here for help.
Role admin - can manage project (set roles, components and version)
Role developer - have all write permission
Role reader - can only see the issues and add comment
other roles - special cases. Mostly, these roles are not mentioned in permission/ notification schemes and have no meaning. But for example when there is added an approval process, then you can use role Approver
Your project has available roles: reader, user and admin.
To create an extra group, please contact TDS Support - we are here for you!

Column
width 50%

Expand
title Permissions

Section

Column
width 50%
Permissions
Here is set how
In permission section you can see how your project rights
are
actually
works.
Can be changed only by Jira admins.
By default, rights are connected mostly to Project roles, but can also add to group or individual users.
Project admin can set Project roles (see Project role section).
Role admin - can manage project (set roles, components and version).
Role developer - have all write permission.
Role reader - can only see the issues and add comment.
work.
To any changes in permission scheme, please contact TDS Support - we are here for you!

Column
width 50%

This is advanced, additional setting. Don't look here until you understand the basics

Expand
title Fields

Section

Column
width 50%
Fields
Here
In fields section can be set if the fields are mandatory or hidden (this can be done in workflows and screens)
It can be done only by Jira admins
Nothing to see here for beginners
TO any changes in fields, please contact TDS Support - we are here for you!

Expand
title Issue Security

Section

Column
width 50%
Security levels
Extension to Permissions,
In the section you can extend permission (another level of security
.You can hide
) like hiding particular issues.
Example: Your customers can see all issues but no your internal bugs.Security scheme can be set only by Jira admins.
There is no default, all project security schemes are handled separately.
To add security scheme, please contact TDS Support - we are here for you!

Expand
title Notifications

Section

Column
width 50%
Notifications
Defines when emails are send.
On every User can be notified when a particular action occurs - an event (issues commented, created, edited) can be defined who (reporter, assignee, particular user, group ) will receive the email.
Can be set per project.
Jira can spam a lot, so we keep notification schemes simple as possible.Can be edit only by Jira admins.
To do changes in notification area, please contact TDS Support - we are here for you!

Expand
title Development tools

Section

Column
width 50%
Jira project can be
connected to Gitlab
integrated with other application like for example GitLab repositories.
You can see branches and commits from you issue.
You can even create branches from the issue.In case of any question
To integrate your project with other application, please contact TDS Support
Team
Expand
title Test Management
Section
Column
width 50%
Powerful test tool.
Adds separate issuetypes, workflows and fields to your Jira project.
- we are here for you!

And that is all for project setting. And remember, there is a lot more in Official Documentation.

Boards management

Board is a visual representation in project, where you can check your issue with statuses. More information what is a board here.

Let's start with the easiest

way
way "Create a new board":
Boards
Go to Boards (top menu) → View all boards
→
→ Create board (at the top-right of the page)
choose between Scrum board and Kanban board
Go to "To right corner Board" →
configure
Configure
Official Board documentation

Image Added

Expand
title General

Section

Column
width 50%
Name - self-explanatory.
Administrators - users who can set-up configuration section. Administrators can't change the mail filter.
Filter - the main filter is set during the board creation. It is an eider project board ("project = 'XYZ") or board based on my, existing filter ("project = XYZ and component = this one and label = some"). Only board owner can change the filter. Jira's admins can change ownership of the filter
Sharing - accessing project and the boards is often the same. But board admin can change it.
Kanban sub-filter - you can hide here the issues which are already done. Don't change the default unless you know what are you doing.
If you miss some issues on board, check the filters.

Expand
title Columns

Section

Column
width 50%
Boards are a different view of the projects. In project workflow you define statuses, but here you can redefine in way which personally suits you the best (As developer you might not be interested in planning, analyzing phase).
Here you can set columns on which are the workflow statuses mapped.
You can map several statuses into one column.
Issues with status, which are not in any column, are not on the board at all.
If you miss some issues on board, check the columns.

Expand
title Swimlines

Section

Column
width 50%
Here, you horizontally sort issues on board
You can make swim lines base on predefined types (assignee, story) or n your own, more complex filters (assignee = 'XYZ' or assignee = 'ABC')

Expand
title Quickfilter

Section

Column
width 50%
Reduce number of visible issues on board to see what is really important to you

Expand
title Card colors

Section
Issue visualization by color based on queries, issutypes, stories, ....

Expand
title Working days

Section
Set up working days of the week and holidays

Expand
title Issue Detail view

Section
If you clock on any issue on board, the detail issue view is shown.
Here you can configure what is important for you to be visible on board.

...

Page tree

Versions Compared

Old Version 26

New Version Current

Key

Project

settings

Details

Issue types

Issutypes

Users and Roles

Don't

manage users it here!

User management is solved via TDS Portal. In most cases, you shouldn't edit this page at all. Look here for help.

Permissions

This is advanced, additional setting. Don't look here until you understand the basics

Boards management

Board is a visual representation in project, where you can check your issue with statuses. More information what is a board here.