Appearance
Fix unattributed effort
When Flowstate sees someone working but can't tell which project the work was for, it puts the time in Unattributed. That time isn't CapEx or OpEx, so you can't submit the week until you've moved it.
You need to be the team's manager, or an approver in its review workflow. Linking a project for your whole organisation from the week needs permission to override or approve effort, and changing that link later on the Roadmap needs access to edit projects — ask your Flowstate admin.
Unattributed, Non-project work and Untracked
| What it is | Stops you submitting? | |
|---|---|---|
| Unattributed | Work Flowstate saw on the day but couldn't tie to a project — tickets with no linked project, and code with no ticket. | Yes |
| Non-project work | Time you've decided belongs to no project. Only a person puts time here, never Flowstate. | No |
| Untracked | Not a row in the week. In finance reports, it's pay for days no activity accounts for. | No |
Move unattributed work
- Go to Delivery → Effort reporting → My teams, and pick the team and week.
- Select the arrow beside Unattributed (Show tickets). It lists Tickets with no project and Pull requests and commits not linked to any project.
- For a ticket that belongs to a project, open the ticket's menu, choose Attribute to project…, pick the project and select Attribute ticket. This moves only this ticket, for only this week.
- For tickets marked Unlinked, select Unlinked, choose the Flowstate project and confirm Link project. Future work on that project then lands in the right place, and its past effort moves too, for every team.
- For code, choose See this person's unlinked pull requests. Link each one to its project there. See Link pull requests to tickets.
- When Unattributed is empty, submit the week.
Stop it coming back
| Cause | Fix |
|---|---|
| A project in your tool isn't linked to a Flowstate project | Link it on the tool's tab under Delivery → Roadmap, or from the Unlinked tickets in the week. Turning on Auto-create Flowstate projects links new projects as they arrive. |
| People file tickets under the wrong project, or none | Ask them to file tickets under the right project in your tool. |
| Code doesn't mention a ticket | Put the ticket key in the branch name or pull request title. See How a pull request is tied to a ticket. |
Unmatched people don't show as unattributed
If someone's account in your project tool or GitHub isn't matched to them in Flowstate, their work doesn't count at all. Check Settings → Integrations → User attribution.
Add someone who's missing from a team's week
A person only appears in a team's week while they're allocated to that team. Until they are, their effort doesn't count towards any team, and finance sees them on Unclaimed.
You need access to change people.
- Open the person's side panel, for example from the People tab.
- Select Schedule.
- Under Teams, select Add.
- Choose the team.
- In Change Team, choose whether all or part of their time moves, and set the Date of change to when they joined.
- Select Confirm Movement.
More in Employees.
At month end
Finance can see what's still unattributed across every team — broken down into unlinked projects, loose tickets and projects missing a cost centre — from Finance → Capitalisation → Projects. See Clear unattributed effort.
If something's not right
The same person keeps coming back as unattributed. Their tickets aren't under a linked project. Link the project, or ask them to file tickets under the right one.
I moved a ticket, but it's back next week. Attribute to project… only changes this week. Link the project instead, or fix the ticket in your tool.
Code is unattributed, but its ticket is on a project. The branch or pull request doesn't mention the ticket in a way Flowstate can read. With Jira, pull requests aren't tied to tickets automatically — link them by hand. See Link pull requests to tickets.