Should Jira story or bug be created when troubleshooting third-party software?

Viewed 19

We have our own custom software (CS) that utilizes a third-party API to start a third-party software X that does a certain function and reports back to our CS. There is a certain bug somewhere in that chain of actions.

To troubleshoot I decided to start software X manually without using CS at all. I found an additional bug in X itself. I had to call support since it's a third-party software, so they could troubleshoot.

Should I a story, bug, task for this situation when troubleshooting third-party software which might be related to our CS issue in retrospect? I thought I should create a task (or bug?) "Troubleshoot a bug in CS" and have linked issues, in which each link issue is a task (since I'm debugging third-party software)?

0 Answers
Related