Project allocation

Inspiration

Primary inspiration is from the tempo timesheet and tempo planner which are too heavy for a very small team (1-5 users). Our idea is to simplify capacity planning to the essence: no accounts, no teams, no allocations per day. You can choose a time period which suits you and then set planned time spent for project members.

What it does

Basically you can create a report for a specific time period on a project, add users into this period and set planned time for the user allocation. Then you can recalculate real spent time from jira worklogs on specific issues. Additionally you can view graphs per user how accurate their real spent time is.

How we built it

Forge app with Custom UI using atlaskit react packages. On the backend (resolvers) we call Jira REST API and Forge Storage API.

Challenges we ran into

Forge app permissions and forge cli tunnel, there were some issues from time to time, but restart of the tunnel worked.

Accomplishments that we're proud of

What we learned

Forge is awesome for small apps in MVP version which we want to test on Jira marketplace to see market fit. Custom UI works well for pages and UI kit is usable for small and simple panels. Jira REST API has good documentation and is easy to test (basic auth with user email and api token).

What's next for Project allocation

We have several new features in the backlog, which we want to implement before publishing into marketplace.

• store reports isolated between project on the same Jira instance (currently it's shared)
• distinguish over and under delivery of spent time with colors
• allow addition of custom measurable column with Jira JQL filter (e.g. development planned/real spent time, or internal planned/real spent time)
• store position on report switcher between refreshes
• create new report by copying of the current
• use icons from atlaskit instead of unicons to make design consistent

Built With

• atlaskit
• react