Ticket Conversion & Tracing from Board to Board - is it possible?

[Elizabeth (Ellie) Rentmeester]

When converting a ticket created in Board A, that I decide to move Board B - is there any way that I can trace where the ticket originally came from? I would want to know that originally that ticket resided in Board A, and then transferred over to Board B. 

I understand that you can "clone" a ticket in jira, which will create the same ticket and link it to the original.  I want to avoid doing that for reporting purposes. 

Does Jira store this tracking information somewhere? Is there any way I can follow the trail of the ticket when being moved in between separate boards? 

[Nic Brough -Adaptavist-]

Not directly, because boards are not containers for issues.  There's no "move from board to board", it doesn't happen.

Boards select a set of issues to display with a filter.  An issue is on board A when the filter for A selects for it, and it's on B when the filter for B selects for it. 

When you change the data on an issue, the boards may change whether they select it or not.  Having mutually exclusive filters on boards can make it look like an issue "moves", but it isn't moving at all, it's stopping being selected by one board and starting to be selected by the other.

There is a full record of all the changes to issues that might make that happen, but the boards an issue appears on is not recorded (because it can change with data changes on the issue and board changes)

[Max Foerster - K15t]

Hi Ellie,

first of all, it's important to keep in mind that an issue belongs to a project and not a board. A board is just a collection of issues based on a filter (so it can even collect issues across multiple projects) and if you move an issue from one project to a different project, you can see this activity in the "History" tab of the issue :) if you want to track on which board the issue appears or not, that's difficult if not impossible as you would need to track which filter will include the issues as a result and that's not that kind of information Jira is and should store :) So depending on how you set up your boards so far (e.g. project-based) you could possibly track the "movement" of the issue. I hope that clears things up a bit.

Best, Max