Versions Compared

Old Version 2

changes.mady.by.user Bob Swift

Saved on

compared with

New Version 3

changes.mady.by.user Bob Swift

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

No Format
titlework.csv
"Issue","Id","Start","Time spent","Time spent (seconds)","Author","Update author","Created","Updated","Comment","Visibility"
"ZWORK-1","22574","2013-07-29","3 hours, 30 minutes","12600","automation","automation","2013-07-29","2013-07-29","My work log entry","Developers"
"ZWORK-1","22576","2011-01-02","1 day, 1 hour","90000","automation","automation","2013-07-29","2013-07-29","",""
"ZWORK-1","22577","2011-01-01","3 hours, 30 minutes","12600","automation","automation","2013-07-29","2013-07-29","","jira-users"
"ZWORK-2","22578","2013-07-29","3 hours, 30 minutes","12600","automation","automation","2013-07-29","2013-07-29","My work log entry","Developers"
"ZWORK-2","22580","2011-01-02","1 day, 1 hour","90000","automation","automation","2013-07-29","2013-07-29","",""
"ZWORK-2","22581","2011-01-01","3 hours, 30 minutes","12600","automation","automation","2013-07-29","2013-07-29","","jira-users"
Tip
titleUsing runFromIssueList for deleteIssue

This is a special case that needs a slightly different approach in most cases. Delete errors can occur if you have subtasks in your project since when an issue gets deleted, it deletes its subtasks, but the subtasks may still be in the list to process. They will generate not found errors when they get processed. So, for delete processing, use JQL that includes issuetype in standardIssueTypes(). If trying to delete all issues in a project, don't use the shortcut way of just using --project, but use JQL instead.

Jira Legacy
serverJIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a-302c-339f-958b-015e107badcd
keyJCLI-418
has some related tips on deleting large numbers of issues.