The research issue then automatically closes but provides no context AND NO LINK back to the research issue. How do I add a link to the newly created defect AUTOMATICALLY?
I'm afraid you have not given us any context here. Research issues and defects are not standard JIRA issues, so you've added them, and you'll need to explain what they are for and how you've configured them. And then when it "automatically closes", what you mean by "no context" and what you mean by "no link" (especially as that sentence appears to say that you're expecting an issue to link back to itself?)
Nic, let's say that the research workflow has two transitions (each of them displays a button to choose to create an issue type). Let's say the workflow has led us to the step where the user can now click on "open defect". The open defect transition automatically opens an issue type of defect in the background but does not display any description or link to the other issue. That's the problem. No other context is needed to solve the problem. if you can't answer it then close your answer.
Right, now you've partially explained a load of stuff you had not bothered to explain before, we can try to help.
>the research workflow has two transitions
Ok. From which status? To where? (Not that we actually need that particularly, having worked through the rest of your update, it's just pointing out that you did not tell us that before, and that you are still not giving us everything)
>(each of them displays a button to choose to create an issue type).
JIRA does not create issues other then by using the "create" function. I now have to guess that you mean you have added 3rd party post-functions that create other issues.
But you have not told us whether these are creating issues or where, or if they are sub-tasks of the current issue.
>Let's say the workflow has led us to the step where the user can now click on "open defect".
>The open defect transition automatically opens an issue type of defect in the background
Ah, ok, we get a bit more useful information. But still no indication of whether it's an issue or a sub-task.
>but does not display any description or link to the other issue.
>That's the problem. No other context is needed to solve the problem.
The original context had none of the information needed to even begin to answer, which is why I asked.. Your comment was far more useful and informative and means I can take a swipe at an answer:
Thanks Nick, see you were able to answer my question making some reasonable assumptions based on your experience with other carriers. well done. Your condescending tone is not what I would expect from a member of an Atlassian organization. Perhaps a modicum of patience would help? Or perhaps, can you just not pick up any tickets that you're not willing to put forth some form of decency? Thanks!
>see you were able to answer my question making some reasonable assumptions based on your experience with other carriers
No. I was able to guess what you meant after you provided more information.
>Your condescending tone
Fair point, I do get condescending when people are rude to me when it's pointed out to them that they have given little or no useful information and I'm asking for more detail.
Maybe next time you're asked to expand on a question that cannot be answered, you would have the decency to answer it without insulting the person trying to help you?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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