Calculates Users Karma, estimates risk of an issue to be reopened which allows to optimize code reviews and testing processes

Calculates Users Karma, estimates risk of an issue to be reopened which allows to optimize code reviews and testing processes

Calculates Users Karma, estimates risk of an issue to be reopened which allows to optimize code reviews and testing processes

Set transitions that are bad for you

Spend less time testing low-risk issues!

Increase your personal karma

Set up what Transitions get you closer to delivery and what don't. With Autofill functionality it's a matter of a minute! Depending on Transitions the plugin will calculate User Karma and Issue Risks.

There are always issues that are more likely to be reopened than others. Depending on who was working on an issue Karma can calculate the odds it will be reopened. Concentrate on those with high risks!

Engineers love being best, they will struggle to make their karma higher. That's what we need! Small number of reopenings means high team velocity. Let them fight for the quality!

More details

Estimates risks of issues to be reopened which allows to optimize reviews and testing processes. As a result this shortens your release cycle.

A few ways of using Karma:

Find out whether an issue will be reopened or will have bugs

Gamify development process: such a drag when your karma is brought down by recent Reopen!

Reviews for cloud

100% means that a task or a developer didn't have any Reopenings at all. By Reopening I mean any "negative" transition backwards (from Done to Reopened, from Closed to In Progress, etc). Which of the transitions are "negative" is determined by administrator.

I don't think so. After JIRA 7 broke backward compatibility we don't feel a lot of warmth about this product. But we can open the sources of this plugin if someone is willing to re-write it for JIRA 7.

**UPDATE:** JIRA 7 compatibility was finally added.

Reviews for server

100% means that a task or a developer didn't have any Reopenings at all. By Reopening I mean any "negative" transition backwards (from Done to Reopened, from Closed to In Progress, etc). Which of the transitions are "negative" is determined by administrator.

I don't think so. After JIRA 7 broke backward compatibility we don't feel a lot of warmth about this product. But we can open the sources of this plugin if someone is willing to re-write it for JIRA 7.

**UPDATE:** JIRA 7 compatibility was finally added.

Reviews for Data Center

100% means that a task or a developer didn't have any Reopenings at all. By Reopening I mean any "negative" transition backwards (from Done to Reopened, from Closed to In Progress, etc). Which of the transitions are "negative" is determined by administrator.

I don't think so. After JIRA 7 broke backward compatibility we don't feel a lot of warmth about this product. But we can open the sources of this plugin if someone is willing to re-write it for JIRA 7.