Project Service Management - Jira

Issue types

Keep track of different types of issues, such as bugs or tasks. Each issue type can be configured differently.

Scheme: CM: Jira Service Management Issue Type Scheme

Priorities

Priorities are used to indicate the importance of an issue.

Workflows

Issues can follow processes that mirror your team's practices. A workflow defines the sequence of steps that an issue will follow, e.g. "In Progress", "Resolved".

Scheme: Jira Service Management IT Support Workflow Scheme generated for Project CM

Screens

Screens allow you to arrange the fields to be displayed for an issue. Different screens can be used when an issue is created, viewed, edited, or transitioned through a workflow.

Scheme: CM: Jira Service Management Issue Type Screen Scheme

Fields

Different issues can have different information fields. A field configuration defines how fields behave for the project, e.g. required/optional; hidden/visible.

Scheme: Jira Service Management Field Configuration Scheme for Project CM

Jira Service Management Field Configuration for Project CM Default

Settings

Some general project configuration options.

JIRA Mobile Connect: More Info Enabled Disabled (Disable Enable)
Custom fields have been updated. Please perform a re-index.
```
[[JMC sharedInstance]
configureJiraConnect:@"https://matesinternational.atlassian.net/"
          projectKey:@"SUP"
              apiKey:@""];
        
```
Add the above line of code to your App.

API Key
Active:
If unchecked, unauthorised clients have access to create (not view) issues.

Reset API Key

Resetting the key will block access to any App already using the current key

Crash Reporting

Enabled:

If unchecked, crash reports will be ignored by JIRA. For high-volume crash reporting, we suggest you integrate JMC with HockeyApp

Versions

For software projects, Jira allows you to track different versions, e.g. 1.0, 2.0. Issues can be assigned to versions.

This project has no unarchived versions. Add a version

Components

Youre using Jira components to group and assign work around sections specific to your project. Learn more about Jira components

Active Directory Feras Wilson
Analytics and Reporting Service Feras Wilson
Billing Services Feras Wilson
Cloud Storage Services Feras Wilson
Data Center Services Feras Wilson

Showing 5 of 16 components. Show all

Roles

Jira enables you to allocate particular people to specific roles in your project. Roles are used when defining other settings, like notifications and permissions.

Project lead: Feras Wilson
Default Assignee: Unassigned
Roles: View project roles

Permissions

Project permissions allow you to control who can access your project, and what they can do, e.g. "Work on Issues". Access to individual issues is granted to people by issue permissions.

Scheme: Jira Service Management Permission Scheme for Project CM
Issues: None

Notifications

Jira can notify the appropriate people of particular events in your project, e.g. "Issue Commented". You can choose specific people, groups, or roles to receive notifications.

Scheme: Default Notification Scheme
Email: Change jira@matesinternational.atlassian.net

Development tools

Integrate your development tools with JIRA to allow users to create branches right from their JIRA issues and to provide visibility into commits, reviews, builds and deployments.

View permission:
- Project Role (Administrators)
- Project Role (atlassian-addons-project-access)
Applications:
- GitHub
- GitHub Actions
- GitHub Actions

Project settings

Summary