Hi all,
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.
Problem description:
--------
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:
- A or B will not be able to create tickets in a project controlled by us, but they will have to create them in projects controlled by the assignee. In the case of the team X, the issues will often be changed on fields such as the reporter, the project, the description, they will be closed, and we will lose any track of them.
- The A team user will require rights in a larger number of Jira queues. In case it is compromised, the data that can be leaked would be much higher. This may not be a problem because the complexity of the additional mapping account owner – Jira queue probably will make the integration even more time consuming and it will be more convenient to just wait for B.
--------
How would you address this problems?
Can somebody help me implement this in several Jira environments?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.