Fixes #108 - Duplicating first activity capacity

[sgtwilko]

Fixes #108 where we were including the first activities capacity twice in the calculation, which for many people seemed to double it. Have updated my testing scenario to show this.

(We've already fixed 80, but I didn't link it correctly, so Fixes #80 )

[sgtwilko]

@yanivsegev This feels like the last bug I introduced for 2.0, so I'm going to look at adding another couple of features after this. Anything you particularly want to see added?

[yanivsegev]

@sgtwilko Your contribution is much appreciated! I was thinking of removing the "rearrange" button and start moving towards React as my next goal. What other new features have you thought about?

[sgtwilko]

Hiya @yanivsegev

I'd certainly be nice to move to React with Typescript, and moving to the new Azure DevOps SDK. However I think that'll probably be a longer term project.

Short(er) term:

• Indicate the work item type (I have this working locally)
• Add configuration option for hiding team non-working days
• Show all users who have non-zero capacity for the sprint.
• Add configuration option to Allow teams to say they don't use tasks (basically allow existing functionality on Stories, hoping that would just be a case of "swapping" the types around on project load)
• Allow users to click on the plan to mark a day as holiday
• Allow users to click on the plan to add non-workitem events (I'd love to be able to put in that half my day will be taken up with meetings so I don't over plan!)

These I think would really help as you can only effectively plan if you can see you availability.

[yanivsegev]

Sounds good. Thanks!

[sgtwilko]

@yanivsegev

I'll get the following three in a PR in the next day or so:

• Indicate the work item type (I have this working locally)
• Add configuration option for hiding team non-working days
• Show all users who have non-zero capacity for the sprint.