https://github.com/cptanalatriste/inflation-tracker-extension
A tool for tracking priority inflation on JIRA repositories from Chrome browsers
https://github.com/cptanalatriste/inflation-tracker-extension
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.5%) to scientific vocabulary
Keywords
Repository
A tool for tracking priority inflation on JIRA repositories from Chrome browsers
Basic Info
- Host: GitHub
- Owner: cptanalatriste
- Language: JavaScript
- Default Branch: master
- Homepage: https://cptanalatriste.github.io/inflation-tracker-extension/
- Size: 512 KB
Statistics
- Stars: 0
- Watchers: 2
- Forks: 2
- Open Issues: 0
- Releases: 2
Topics
Metadata Files
README.md
TheFed
Some reporters inflate priority to get their issues fixed. When they do that, you as a developer can spend time on issues that are less important than other open issues. This Chrome Extension helps you identify reporters who do this.
Installation
The Chrome Extension is still under development. To install it, download the extension code, unzip it and load it as an unpacked extension following this procedure.
Features
After installing the extension, the inflation tracker button will be available in your browser. After clicking it you will see the following:
Immediately after installing the extension you should configure the options according to the characteristics of your bug reporting process. Here's a brief descriptions of the options available:
- JIRA host: The URL of your JIRA system. For example, tha Apache Software Foundation uses https://issues.apache.org/jira
- Inflation penalty: The extensions works based on the concept of "Reporter Reputation". If the priority assigned by a bug reporter is changed later during the patch development process, his reputation score is diminished. This parameter defines the penalty per infraction.
- Maximum results per request: Under the hood, the extension makes heavy usage of JIRA's REST API: This parameter defines the maximum number of issues returned per request.
- Minimum acceptable reputation: Each reporter gets a "thumbs up" or "thumbs down" label based on their reputation score. This parameter defines the minimum reputation score for a "thumbs up" label.
- Project: The name of the project you're working on.
- When you finish working on an issue, you update the status to: We use this information to identify the "important" priority corrections that impact the score. For example, if this parameter is set to "Resolved" —the default— any priority correction made by a "Resolver" will impact the reporter's reputation.
Once you have set proper values for all this parameters, you can click on the "Load Issues" button to obtain a list of open an unassigned issues sorted by reporter reputation, reported priority and creation date:
Per issue, you can see the reputation score of the reporter in the "Score" column. Also, we provide a "View" button —the magnifier glass— which can open the issue on the current active tab. After the issues have loaded the "Reputation Report" button is activated, which shows the list of reporters for the issues in the inbox sorted by reputation, including their "thumbs up" status:
The Priority Inflation Game
This tool is the outcome of a research project on game-theoretic analysis of software processes. If you want to get into details, feel free to visit our project page.
Questions, issues or support?
Feel free to contact me at c.gavidia@cs.ucl.ac.uk .
Owner
- Name: Carlos Gavidia-Calderon
- Login: cptanalatriste
- Kind: user
- Location: London, United Kingdom
- Company: @alan-turing-institute
- Website: https://carlos.gavidia.me/
- Twitter: cptan_alatriste
- Repositories: 74
- Profile: https://github.com/cptanalatriste
Systems engineer by training, software developer by trade. Research Software Engineer at @alan-turing-institute .
GitHub Events
Total
Last Year
Issues and Pull Requests
Last synced: 12 months ago
All Time
- Total issues: 1
- Total pull requests: 0
- Average time to close issues: 2 months
- Average time to close pull requests: N/A
- Total issue authors: 1
- Total pull request authors: 0
- Average comments per issue: 2.0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- relgames (1)