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; } } }

Collaborating with diffrent types of Jiras

Malin Nordqvist

I am a UX designer and I work in a large company with different roles (Developer, UX). We work in agile development teams and use SCRUM. Are there any pros and cons to working with different types of Jiras when you work closely with developers? For now, we use 'UX-task' on the DEV-Jiras. We are discussing the pros and cons with having UX jiras and DEV jiras separate. Can anybody give me some input? Thanks

Accepted answers

miikhy

Hi and Welcome on Community!

In most cases it's easier to have a single instance of Jira supporting different type of work than duplicating the instances. It also gives quite a huge save on licence fees in most cases. That being said there is no real problem with multiple instance but most features of Jira Agile are meant to be used in a single instance and my concern would be to loose some of those features if splitting the work.

My recommendation if you want to separate UX and Dev task would be either to have two issue types so they can have their own configuration (workflow, fields...) or even two projects if it's more relevant to you.

From past experience in major banks, insurance companies, leading Development programs, we kept a single project with 2000-5000 user stories and did split them into dev, UI, UX, QA tasks/subtasks. That's how I'm the most comfortable!

Hope this helps!

Cheers

All comments

miikhy

Hi and Welcome on Community!

Hope this helps!

Cheers

Malin Nordqvist

Hi! Thanks for a great response. We do have UX-task on the DEV-jira which I find really helpful. The UX Manager would preferable like to have solemnly UX jiras and Dev jiras so I am making a list of all the pros and cons with using either type. Cheers

miikhy

I get that!

It's really two way of thinking and none of them is a real mistake but again, I definitely feel like Jira is meant to share configurations or to have independant types/projects on a single instance. I've rarely seen more than 2-3 instances in very large companies and the reason has always been "we did not know there was another instance".

If you want a more detailed audit of your situation you can also get in touch with a local partner (https://www.atlassian.com/partners) which can help quite a lot if you're having hard time with the technical part of it!

Best luck!

Cheers

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk