I have a question regarding Jira rickets.
I have a project description, can you please help if this is possible and how to best do this.
The concept of substituting issue assignation with issue creation in other people’s projects because we can’t assign them to a team looks strange to me. In a standard ticketing system you create a ticket and you assign it to a team, you can create a sub-ticket only when it is required, for example when you decide to split the work.
We will need to keep this well defined in order to avoid ending up in having to open a number of issues for standard communication. Every time we need to ask something to somebody, they will require us to open a new issue, it will become very difficult to manage. A new ticket is opened only when a piece of work or a consultancy is required from another team.
The reciprocity will present us some additional problems, such as:
How would you address this problems?
Can somebody help me implement this in several Jira environments?
Introducing Jira Cloud for Excel Here at the product integrations team at Atlassian, we are thrilled to announce the new Jira Cloud for Excel add-in! This add-in lets you export Jira data directly ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events