Skip to content

Tinkoff/jira-helper

Repository files navigation

Build Status

“jira-helper” features

version 2.6.0

Issuing project tasks

All tasks are created at github issues

Before creating a task, please make sure that a similar task was not created earlier. Please be sure to check closed tasks - there is a chance that your request has already been fulfilled and will be released soon.

Requesting a feature

Create a new task

After adding description, please specify the following attributes only:

  • Labels: feature
  • Project: jira-helper

Requesting a fix

In case some feature doesn’t operate as expected.

Create a new task

After adding description, please specify the following attributes only:

  • Labels: invalid, [cloud jira, jira 7, jira 8] – specify in which JIRA version the problem is reproduced.
  • Project: jira-helper

Adding a description for a bug/problem

Create a new task

After adding description, please specify the following attributes only:

  • Labels: bug, [cloud jira, jira 7, jira 8] – specify in which JIRA version the problem is reproduced.
  • Project: jira-helper

List of most often used labels

labels Meaning
feature new feature
invalid a feature doesn’t work as expected
bug a problem/error, please be sure to specify a JIRA version label, where one could reproduce it
jira 7 reproducible in JIRA 7.x.x
jira 8 reproducible in JIRA 8.x.x
cloud jira reproducible in JIRA Cloud

Installing the extension for development purposes

Execute:

npm run bootstrap
npm run dev

In Chrome:

Open the menu, choose “More tools”, then "Extensions"

On the "Extensions" page toggle “Developer mode”, press “Load unpacked” in the appeared menu.

Choose the folder where the extension was built, ~/jira-helper/dist.

During development

When code changes Webpack will automatically update the codebase in the dist folder.

Press “Update” in the "Extensions" developer menu and then reload the page, where the extension is being tested.

Maintaining a git branch and git commits

The branch name should start with an associated task number.

Example: 2-title-issue, where 2 is the mandatory task number.

Every commit should have a task number associated with it.

Example: [#15] rename *.feature to *.ru.feature

Please use english language only to name branches and commits.

Publishing information

The official version of the extension is published in "Chrome WebStore"

The extension is published after the release is assembled at github

Release version is the same as the application version in package.json package.json and the version published in "Chrome WebStore"

Minimum required Chrome version is >= 55