Documentation of tasks of Kanban-Board and data export

[Simon Scharpf]

Hello Community,
I have two questions:

1) How is the data of the individual tasks of a "Next Generation Project" stored?(documentation of all tasks)?
Can the data of all tasks (i.e. the whole Kanban board) be exported?

2) Can individual task data be read/exported? For example the history of the states with timestamp?

Thanks in advance

Simon

[Andy Heinzer · Accepted solution]

Hi Simon,

The tasks you see on a next-gen board are being stored as issues within Jira.  The most straightforward means to export these would be to search for those issues.  Next-gen boards only show issues in that project.  So we can tell that you would likely need to just search for the issues in that project.  You can do this by going to the Filters > Advanced issues search or visiting the URL https://[yourcloudsite].atlassian.net/issues/

From there you can use an advanced search such as

project=ABC

where ABC is the project key in question.  This will return to you a list of all the issues on that board.  This search page also has an export function, so that you can export these issues into another format such as csv.  However this export method doesn't provide a complete issue history, only the issue data that exists for those issues now.

If you happen to need the issue history (and it sounds like you do) there is still a way to obtain that, but it is more complex.  You can use the REST API in order to get the issue history.  This can output the issues into a json format. 

To do this for a single issue you can call the endpoint GET /rest/api/3/issues/{issueIdOrKey} and then use the path parameter of expand=changelog.  This is more complex to do, but if you use this endpoint you would have to repeat that call for each issue on the board.

Alternatively you can call the endpoint of GET /rest/api/3/search and again use the expand=changelog path parameter.  But to use this endpoint you also have to pass in a jql path parameter that searches for issues on that board.  In this case, you can use the JQL search from the first step and your REST call might look something like this

curl -v -D- -X GET \
-H "Authorization: Basic [redacted]" \
-H "Content-Type: application/json" \
"https://[yourCloudsite].atlassian.net/rest/api/3/search?jql=project=ABC&expand=changelog"

This is most likely what you would need to do to export the changelog history of all the issues on a specific board.

Alternative to using an issues search call to first find these issues, there is another REST API point you can use to specifically get back the issues on a board.  Try using GET /rest/agile/1.0/board/{boardId}/issue. However this endpoint does not currently support using the changelog expand path parameter.

Does this help?

Andy

[Simon Scharpf]

Yes, thank you. 

But I haven't tested the complicated waye yet.. 

I have to deal with it in order to possibly ask further questions. 

Thank you

[Mariana_Pryshliak_Saasjet]

Hello @Simon Scharpf 

Can you clarify more - do you need a list of tasks and detailed info about them (assignee, time in status, etc.)?

Regards, Mariana

[Simon Scharpf]

Hello @Mariana_Pryshliak_Saasjet 

like @Andy Heinzer explained, with https://[yourcloudsite].atlassian.net/issues/ i can see all tasks, thats good. The reason I'm asking is that I want to guarantee audit-proof documentation (revision safe) for my board.

Is it possible, to take some users the option to delete a task on the board? Maybe that only the admin can delete tasks? - Keyword: process security, that no task can be accidentally deleted and that all tasks are always available in the overview?

Or is there a kind of bin where the deleted tasks of a board will be "moved" or "stored" and these can be restored if necessary?

Thanks for your answers

[Daniel Ebers]

Hi @Simon Scharpf

next-gen projects use a somewhat lighter kind of permission management - Viewer/Member/Administrator are the roles used.

But, yes, role "Member" for example  does not grant "Delete any issue" to people which are in that role. Instead they would have to be in role "Administrator".

Please also compare with:
https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/#Project-permissions

An deleted issue, however, is deleted permanently.

Regards,
Daniel