Task deligation

[Zaza]

Hello guys, our company is new to jira. We have just started setting up the software to suit our needs and i have a situation i cannot seem to get a hold of. 

So as i understand it, jira sees projects as departments, so there is a project for example called “marketing” and one called “development” which are in reality departments that are taking care of the tasks delegated to them. 

What i would like to do is create a literal project, with all the tasks needed for its completion inside it. Tasks that involve everything from product development to marketing, finance and so on. I want to create tasks in that project, and then give the tasks to the appropriate departments which are created as other projects(i hope i have explained it fairly well). The thing is, jira is not letting me create a task and assign it to a different project so that when a task is completed by a specific department i can see it updated in my project. 

Please let me know if there are solutions to this or even an alternate method of doing it. Thank you very much in advance 

[Trudy Claspill]

Hello @Zaza 

Jira Projects are containers for issues (i.e. work items). Jira Projects can be set up to align to teams (all the work items for a given team), for a work project that spans multiple teams (i.e. from inception, through development and delivery including marketing), or any other organization of work items that you choose.

A work item can exist in only one project at a time, but you can create links between work items in different (or the same) Jira Projects to show that the work is related.

Jira also provides agile boards (Scrum and Kanban) that provide a way to visualize and manipulate work items that are in Jira Projects. Depending on how you set up your Jira Projects, you could have a board that shows the issues from multiple projects.

So, there are a few ways to address your need for a Jira Project that includes work spanning multiple teams.

You could create that one Jira Project with all the work for these multiple teams. You could set a tag on each work item to show which team owns the work. You could have a Board that shows all the work in the project, and also have separate boards for each team that shows only their work.

You could have your one Jira Project with all the work for the multiple teams. You could then create separate work items in each team's project for their work, and link their items to the items in the one Jira Project. You could use Automation for Jira to synchronize the information between the two linked issues.

I personally think that the first option is the better option.

[Dave Mathijs]

Hi @Zaza 

A project is a collection of related issues

A Jira project is a collection of related issues. A project is a way to organise work. The issues can be related in any way that the team desires.

A project can act as a team “to do” list

You can think of the issues of a project as the team’s “to do” list. The issues can be in different states, such as not ready for development, ready for development, in progress and done. Jira therefore contains a record of the team’s work, allowing the team to do things like report on their work.

A project can have a fixed end date or be an ongoing project

A Jira project is not necessarily a project in the traditional sense, which usually has a start and end date. The term “project” is used loosely to include work that has no planned end date. For example, a product that is planned to continuously be improved, with no plan to ever stop work on it. When this course refers to a “project”, it is meant to be a Jira project.

A project has an associated type

Projects have an associated type, depending on how the team wants to accomplish their work. When you create a project, you select its type, such as Kanban or scrum. We will discuss these later in the course. Over time, the team can configure their project to use a custom agile methodology or framework.