nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

The issue with Jira integration

TI - Administrador

I am experiencing an issue regarding the integration of Jira in the company I work for. Currently, the IT department is divided into four subsections: support, data, infrastructure, and systems. I would like to know if there is a more automated way to merge these four subsections into a single project without compromising organization.

Accepted answers

Trudy P Claspill

Hello @TI - Administrador

Welcome to the Atlassian community.

Are these four subsections already using Jira and using separate projects in Jira? Or are you interested in starting to use Jira and wondering about how to set it up for these four subsections?

Syed Majid Hassan -Exalate-

Hi @TI - Administrador

Welcome to the community! This is Majid @ Exalate.

There are so many ways to do this, but really depends on the business need you are trying to address. Some ways I can think of:

have all teams on the Jira instance, and create different projects for each
- then create custom permission schemes to control data security between teams.
- you can enhance the flow by adding automation and integrations between the projects.
create different Jira instances for each team and sync them together using an issue synchronziation solution like Exalate.
- this way you get full autonomy for each team, while maintaining seamless collaboration between them as well.

Hope it helps.

Thanks

Majid

All comments

Trudy P Claspill

Hello @TI - Administrador

Welcome to the Atlassian community.

Are these four subsections already using Jira and using separate projects in Jira? Or are you interested in starting to use Jira and wondering about how to set it up for these four subsections?

Syed Majid Hassan -Exalate-

Hi @TI - Administrador

Welcome to the community! This is Majid @ Exalate.

There are so many ways to do this, but really depends on the business need you are trying to address. Some ways I can think of:

have all teams on the Jira instance, and create different projects for each
- then create custom permission schemes to control data security between teams.
- you can enhance the flow by adding automation and integrations between the projects.
create different Jira instances for each team and sync them together using an issue synchronziation solution like Exalate.
- this way you get full autonomy for each team, while maintaining seamless collaboration between them as well.

Hope it helps.

Thanks

Majid

TI - Administrador

I already have a project created, but my manager would prefer not to have several projects, only one, and for the entire team to use this same project. However, I mentioned to him that it would be easier to have separate projects for each subarea to ensure better organization.

Trudy P Claspill

What is considered "easier" depends on what you ultimately need to accomplish.

Do the teams need to use the same type of project configuration (issue types, fields, screens, workflows)?

Do members of each team sometimes work on other teams' tasks? Or do you need to prevent each team from seeing the other teams' tasks?

Do you need to provide reports that include data for all teams in one report?

Why does you manager prefer to not have several projects?

Why do you think having separate projects would "ensure better organization"?

TI - Administrador

The teams need to use the same project configuration (issue types, fields, screens, workflows)? Yes, in order to create standardized forms for proper user input.

Do team members sometimes work on tasks from other teams? Or do you need to prevent each team from seeing the tasks of the other teams? Yes, although there is a tendency towards team specialization, currently, there is a need for inter-team collaboration.

Do you need to provide reports that include data from all teams in a single report? Considering that the "teams" consist of 1-2 members, there isn't as much need for specific indicators for each of the teams, as the gap between management and operations is relatively small.

Why does your manager prefer not to have multiple projects? To facilitate team monitoring in a unified manner, considering the points mentioned earlier.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud