we currently phase the challenge of projects versus team structures.
we use scrum and partly kanban for software projects, often inside this projects you require infrastruxture work.
the processes for software differs as well from building up infrastructure.
our infrastructure team works inside an own project named infrastructure. each sw peojectis an own jira peoject named for example software2, software 2 ..5
now the question is how to create tasks which should be done inside a project for infrastructure work.
if we create inside peoject our system admins need to work with multiple boards to handle there tasks.
if we create outside in infrastructure peoject we loose overview on project side.
sure we can create2 taska one in project and one on infrastructure and link them.
but when you close the infrastructure ticket you would need to close as well the oroject task.
so how do you handle this ? whatisnthe best practice ?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs