Thanks Nic! I figured as much upon further reading. It's more information for us since we integrate the issues from JIRA into downstream systems and know which node the issue was created on would help us with trouble shooting some data flows. It really wouldn't "solve" any problem for us.
My choice of "problem" probably was quite a bad choice, sorry.
I can phrase "knowing where your data is flowing" as a perfectly good definition of a "problem to solve".
I've seen that done in three different ways very broadly:
Thanks.. sorry for the late response. We don't have a very large DC, but still think that knocking out one node may be the only way to do this. And these calls aren't being initiated by humans, I suspect that upstream process is making a duplicate call but we're still trying to track that down. Thanks again!
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
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