Tracking tasks

Cristy Luis

Hi

New to Jira, coming from IceScrum

My project has a few stories to be completed by specific people outside of the main team.

Management wants this work represented in the project plan so that we can track progress.

I don't want to add these issues to the backlog and the people to the team, because that will interfere with tracking the velocity.

What's the preferred method of dealing with these issues?

Nic Brough -Adaptavist-

Most of us have similar cases and we usually keep the solution as "don't include the items in the backlog/sprint" - you don't want them in there because the backlog is for the development team, and these items need doing outside the team.

Often, people will simply do it with a separate project, changing the project plan so that it includes the dev project and the external project, and using links between issues in the two projects to show relationships.

But another way to do it (especially if you're putting all the issues into one project) is to differentiate the external issues somehow, and then set up the board to ignore them.

An obvious way to do this would be to have your project have a set of issue types such as:  Issue, Bug, Improvement, external-task, and then have a board set up for the developers that says "Project = XYZ and issuetype != external-task.  You could do this with components, labels or pretty much any other field you wanted too.  And even set up a separate board for the external users.