woellchen / sprintanalyzer Goto Github PK

simple but handy: show the issue summaries next to the issue keys

when querying jira for all sprints of a rapidview, it does not include future sprints (not yet started ones)
this requires a new method in the node-jira lib finished first

introduce a blacklist that enables to ignore specific sprints for all actions possible

my idea is to cache full (jira) requests bound to the client connection
hence a reload will invalidate the cache state, forcing to reload data from jira
of course, (almost) static data like the rapid view id can be cached globally, so we have basically two layers of caching
question is if it would be good and when to invalidate that connection cache

would be nice to visualize in some way which issues are completed/incompleted by grouping them or something
one thing would be another graph and the other thing is the issue listing itself in the analyze view

Not every Jira project will have the same way to calculate the velocity therefore I suggest to introduce a project config.

Each project would then be able to configure project specific stuff.
Suggestion for the structure:

{
  "project": "project",
  "velocity": {
    "type": "labels",
    "labels": {
      "size": "value",
      ...
    }
}

Should there be one config file per project or one config file for every project?

Something for later would be, that one can simply create the config for a project the first time the project page is open (maybe even edit existing configs).