We are building a case management solution for a compliance department where there are 2 projects involved. Let's call them "Investigation" and "Products".
The compliance officers will work out of the "Investigation" project. Each new case is opened via a new issue, and each product that is under investigation creates a new "sub-task".
Now, in order not to manually copy information about the products we created a "Products" projects, where each issue is a product, and this project is updated on a weekly basis by running a report from our main database. This will maintain the integrity of the information about the products. Basically, the "Products" project houses each product and all of its information such as ingredients, registration status, owner, product name, etc.. in each issue.
So, instead of manually writing out by hand all of the products information in the "Investigation" Sub-Tasks for each product, we decided to just link the product via a "related to" link in that sub-task.
One of the requirements is that we need to see how many "Investigations" Sub-Tasks contain a specific specific ingredient. The problem, is that the ingredient field is located in the linked issue.
Is there a way to pull this information natively, or with an add-on? We're currently on the cloud, and might be moving to server. Alternatively, is there a way to automatically populated some fields with values of the linked issue into the sub-task?
Use nFeed and replace your Products project entirely when on server.
As best as as I understand it, your setup is this:
investigation issue -> product subtask -> issue link to product reference issue
your goal is to count the number of subtasks, that contain an issue link, to an issue with a specific custom field value?
That's right. In other words:
Investigation Issue with a Product Subtask that has a link to a "products" issue.
Need to see how many sub-tasks have linked issues, where the linked issues contain a specific custom field value.
We're still not sure if we're going on server. Is there a workaround or way to do this on cloud? Ideally something that's workable on both, so we don't have to go back to this if we decide to go on server.
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events