BlueGrove Labs
Help CenterRowCraft – Table Fields for JiraJira Cloud
Support
中文

Using the app

RowCraft data, privacy and permissions

RowCraft is built on Atlassian Forge and runs entirely on Atlassian's cloud. It has no servers of its own, sends no data outside Atlassian (no egress) and uses no external storage. Forge reports RowCraft as eligible for Runs on Atlassian.

Where your data is stored

Data Stored in
Rows of a table field The custom field value on the work item, in your Jira site
Columns, rules, colours and default rows of a table field Jira's field context configuration
Rows of a panel table A work item property on the work item, in your Jira site
Panel table definitions (name, scope, columns) Forge app storage, hosted by Atlassian
Saved report views Forge app storage
Change history of panel tables Forge app storage
Change history of table fields Jira's own change history of the work item
Whether a project shows the RowCraft panel A project property in your Jira site

Table data stays in your Jira site and in Atlassian-hosted Forge storage for your installation. BlueGrove Labs has no copy of it.

Jira permissions always apply

  • Viewing: tables are shown only on work items people can browse. Reports, the search helper and the change history read data as the current user, so people only see rows of work items they are allowed to browse. Sharing a report view shares its settings, never its data.
  • Editing: saving a table needs permission to edit the work item. Panel tables are written as the user, so Jira checks the Edit permission.
  • Searching: JQL results follow Jira's browse permissions like any other search.
  • Administration: the Field tables and Panel tables pages, and all changes to table configurations, require the Administer Jira global permission, checked on the server for every request.
  • Rules: required, read-only and lock rules are enforced by Jira itself through the field's validation, so they also apply to REST API calls, bulk edits and automation.

App scopes

When RowCraft is installed, Jira asks for the following scopes:

Scope Used for
read:jira-work Reading work items and table values for the editor, reports, history and search
write:jira-work Saving panel table rows as work item properties, as the user
read:jira-user Showing people in user columns and rule conditions
read:servicedesk-request Showing tables on Jira Service Management portal requests
read:custom-field-contextual-configuration:jira Reading a table field's column configuration
read:field:jira Finding RowCraft fields and their contexts for search and reports
read:app-data:jira, write:app-data:jira Keeping RowCraft's JQL functions up to date
manage:jira-configuration Creating table fields and saving their configuration from the admin pages (the user must also be a Jira administrator)
storage:app Panel table definitions, saved report views and panel table history in Forge storage
write:project.property:jira, delete:project.property:jira Marking which projects show the RowCraft panel

RowCraft requests no external permissions: it does not call any server outside Atlassian, and people's avatars are loaded from Atlassian.

Deleting data

  • Clearing a table and saving removes its rows from the work item.
  • Deleting a column removes its values from work items in the background after the configuration is saved.
  • Deleting a panel table deletes its rows, search data and change history on every work item.
  • Deleting a work item removes its panel table history.
  • Saved report views can be deleted by their owner or a Jira administrator.

More information