renuo / renuo-chrome-workflow

Chrome extension for the renuo workflow

Renuo Workflow

Installation

https://chrome.google.com/webstore/detail/renuo-workflow/cbdponefdfobikfhoflfnmmcmmoogleo

Summary

Contains the chrome extension to enhance the Renuo workflow, see /app.

Use

grunt serve

for development.

Setup

git clone [e-mail]:renuo/renuo-workflow.git
cd renuo-workflow
bin/setup

Converting Coffeescript to Typescript

npm install -g coffee-script-to-typescript

Deployment

• Download the app.pem from here: https://redmine.renuo.ch/attachments/download/1926/app.pem
• Increase the version number in manifest.json, bower.json, package.json (TODO: automate this).
• Use pack.sh to pack the extension.
• Upload it to here: https://chrome.google.com/webstore/developer/dashboard

Dependencies / Type Definitions

Install a new dependency (e.g. jquery)

tsd install jquery --save

Install existing dependencies:

tsd rebundle
tsd reinstall

More info: https://github.com/DefinitelyTyped/tsd

Tests

Use

grunt test

Concepts

Issue Sorting and Priority

There are 2 different priorities in the system.

• The human readable Priority (e.g. Normal, High, Urgent, etc.)
• Is shared and entered by the customer
  • Is relative in each project
• The backlog priority BP
  • This priority is used to plan sprints (the company backlog, across multiple projects)
  • Enables drag'n'drop functionality

The key problem is that for the product backlog (what will be done next week) we need the backlog priority. However, a customer doesn't want to see that all his tickets are on "Low" priority because they will be planned next week. On the other hand, it would be nice if the BP and the priority would be in sync.

We do the following

• Every BP must be distinct, so the issues can be ordered
• Every priority is assigned to a BP 0 when the issue is created BP when the issue is created (e.g. Low = between 100 and 300, Normal between 300 and 500, etc.)
• When a priority is changed, the BP is not changed (for now)
• When a issue is dragged around, only the BP is changed, not the priority (for now)
  • The new BP will be in the middle of the two jammed issues BP's. If these values are too close to each other, there will be a warning in the user interface (has to be resolved manually)
• In the background (e.g. every 2 seconds), we run a service which will distribute the issues, see BacklogPriorityBackgroundService
  • This service will try to evenly distribute the priorities using a greedy algorithm so that the single issues can be updated separately

CI

https://travis-ci.com/renuo/renuo-workflow