Hi,
Β
Does anybody have experience exporting User stories (Desription, Progress, LOE, % Complete, etc) from the Agile App in a format that will allow us to import that file into Jira and have Jira updated with the same progress?
@briankenez It's been a while since your original post, so you may have solved for this already. While I haven't had direct experience exporting user stories from the Agile App into Jira, I am familiar with the APIs of both tools.
There is fairly good documentation provided by Atlassian on importing issue data from a CSV. Note the details on the Issue Key field: "You can set the issue key for an imported issue. If an issue with a given key already exists in Jira, it will be updated instead."
If you want to set things up to be able to update Jira with progress based on the Agile App, you'll need to modify your Agile App to be able to specificy the Jira Issue Key for each user story, so that you have the cross-reference to be able to update existing issues. You can also build a custom export in the Agile App to both include that Issue Key along with the specific fields you want to bring over.
On the Jira side, I believe you just need to map those fields when you import the file per the instructions on the page above. The mapping will also depend on how you've configured your project in Jira.
I wanted to check if others are facing this specification difference between Grid Card in Additional Insight. When created using a Saved View, the Quick Sum bar feature does not work, but when created using the module directly, the Quick Sum bar works.
Does anyone have any documentation on the trade-offs of having 1 model for all components of planning (service revenue, product revenue, labour planning), vs multiple models 1 for each and a consolidation model to tie it all together?
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-yearβ¦
