Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,369,964
Community Members
 
Community Events
168
Community Groups

How to implement the possibility of closing issue_A from project A, through issue_B of project P.

Hi there,

 

I have the following task that requires your help.

 

Jira instance has a lot of projects, but let's consider two projects now: Project_A and Project_B

 

Each of the projects has a separate business workflow with more than 20 statuses and works according to a certain logic to solve business problems.

 

I need a solution that will allow me to close tasks from project A or B from any status except for To Do and Done. These Jira tasks should be tracked by the operator. 

 

I have an idea to create a separate project (let's say Project P) and use this project to close tasks from project A or B.

 

Here is the logic:

 

  1. A user creates an issue_ABC in Project A
  2. A user moves issue_ABC to status_X1
  3. A client wants to cancel the task and asks the user to close issue_ABC
  4. A user creates an issue_BCD in a new project_P
  5. A user selects issue_ABC (to close it)
  6. A user backs to issue_BCD interface
  7. A user hits “Close” button in issue_BCD
  8. Jira should send a request to close issue_ABC
  9. Issue_ABC should be sent to “Achieve” status 
  10. Issue_BCD should be sent to “Close” status



I cannot implement the additional "Archive" status in project A so that I can immediately send the tasks that the client refused there.

 

Because Jira contains many projects (more than 15) and it will be difficult for the operator to track customer refusals.

 

Moreover, if the task is canceled, it is necessary to attach a file with the reason for the failure.

 

The question is how to implement the possibility of closing issue_ABC from project A, through issue_BCD of project P? 



1 answer

0 votes

Hi @Daniyar Kenensarinov 

I think you should look towards Automation for Jira Add-on from the Atlassian Marketplace, that will help you around this problem. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events