useshortcut/project-analytics

Visualize Clubhouse Project data using Google Charts.

project-analytics's Issues

Add visualization of story dependencies

We use story relationships (blocks and is blocked by) to express dependencies. It would be tremendously useful to visualize these relationships in a DAG, as this would show the critical path. Knowing which story is a head-of-line blocker helps understanding where to channel efforts for maximum productivity.

A visualization in the form of a DAG makes this obvious: the node with the highest in-degree represents the story with the most bang for the buck.

Have you considered such an enhancement?

Documentation for adding clubhouse api token is incorrect

When I followed the instructions on your page I saw that you ask users to:

Add your Clubhouse API token as an environment variable.
(Go to Clubhouse > Settings > Your Account > API Tokens to create one.)
run CLUBHOUSE_API_TOKEN="MY TOKEN"`

when it should be export CLUBHOUSE_API_TOKEN="YOUR API TOKEN HERE"

Clubhouse API V2

Hi Andrew,

I just wanted to let you know that we've released Clubhouse API V2. While V1 will continue to be supported, V2 exposes endpoints for several new features such as Teams, Milestones, and Categories.

Thanks,
Camille

Missing `data` Directory on Fresh Clone.

This is a super minor issue, but for the less technically inclined, it can introduce unnecessary barriers.

On a fresh clone, the data directory does not exist.

Executing node fetch.js all results in the following top-level exception:

Fetching projects...
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open 'data/projects.js'
    at Object.fs.openSync (fs.js:582:18)
    at Object.fs.writeFileSync (fs.js:1301:33)
    at saveProjectsToFile (/.../project-analytics/fetch.js:210:6)
    at Request._callback (/.../project-analytics/fetch.js:254:5)
    at Request.self.callback (/.../project-analytics/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:192:7)
    at Request.<anonymous> (/.../project-analytics/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)

The README.md should be updated to include the step to create the directory. Or better yet, the repository should include the empty directory, with a .gitignore.