|
I would find this useful as well. I am using Microsoft Project to schedule projects. I use it mainly for it's ability to level resources and manage moving tasks with interdependencies. In any case, I export task info (summary, description, assignee, due date) from MS Project into a CSV file that I import into JIRA. It would be great if JIRA's CSV import process could identify duplicate issues by summary and update each associated field.
If this is implemented, it would be nice if the Excel output of the Issue Navigator could, when saved as CVS, be correctly read by the CVS importer.
That way, you could export to Excel, edit the file in a meeting away from the server, and then just import it to update with the changes. Side Note Hello Matt,
there is already an issue for your request, but without the excel stage. Cheers Bettina Hi vote for this feature!
Absolutely a time saver. My use case is as follows: We use Agile methodology called scrum, and need to manage user stories in JIRA. I find that I refactor the stories quite frequently - touch a lot of stories and often they have to be updated/rewritten in groups based on new information. This workflow is much more efficient but also superior in that you can edit the user stories in context: 1: find all the related stories Please up the priority on this request. A rough ETA would be nice. Thanks. Cheers I've hacked together a python client that can update the export CSV Jira issues using XML-RPC.
We are using it internally, but the "paint is still a bit wet". There should be adequate unit tests to enable others to extend this to support their needs. I believe that after you have configured it as per the README it should just work for your environment and that you won't have to write any more code for it. Ideally I see Atlassian providing a web based tabular update capability which would reduce the need for this tool. Is this something that Atlassian wont to pick up and provide support for? Ideally I would like a web based spreadsheet opened for selection issues and specific values from those issues.
Then I can make adjustments in the spreadsheet and "apply" the changes in one go. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Critical
Extend CSV import to update already imported issues
extension it could be made into one.
I must admit that no one has actually asked for this before.
One way to programmatically update issues is to write a SOAP client that does this. The client can parse the CSV file and then update the necessary fields through SOAP. For more information on the SOAP acess to JIRA please see:
http://confluence.atlassian.com/display/JIRAEXT/JIRA+RPC+plugin
Would this work for you?
I guess getting CSV to update issues would be possible, but given the nuber of feature requests that we have, it might take us a long while ot get to this.
I hope this helps.
Thanks,
Anton