Managing Tasks
Audience: privacy, GRC, security, and AI governance teams who assign and track remediation and follow-up work in Relyance AI.
Overview
Tasks are the work items your team creates and tracks in Relyance AI - a vendor contract to chase, a control to fix, a risk treatment to carry out, an AI agent to review. Each task has an owner, a priority, a due date, and a status, and can be linked to the record it's about: an asset, a risk, a policy violation, an AI agent, a vendor, an assessment, and more. Break larger work into sub-tasks, capture your own fields with custom fields, attach evidence, and point to an external ticket. When your team works in Jira, push a task there with the Jira Workflow Connector and keep it in sync.
You find Tasks under Act → Tasks in the left-hand menu, next to Issues.
Why use tasks
- One place for follow-up work. Remediation steps from a risk, findings from an assessment, and clean-up on an asset all land in one list you can filter, group, and save views of.
- Work tied to the record it's about. A task linked to a risk, policy violation, or AI agent opens that record in one click, so whoever picks it up has the context.
- Accountability for audits. Every task records its creator, assignee, due date, and status history, and carries comments and attachments as evidence of what was done.
- Fits how your team already works. Add your own custom fields and tags, link to an external ticket, or push the task to Jira through a workflow connector.
How tasks work
| Part of a task | What it is |
|---|---|
| Title | Required, up to 200 characters. |
| Description | Rich text - context, steps, or acceptance criteria. |
| Priority | Required. Defaults to Medium. |
| Due | Optional. Can't be in the past. |
| Assignee | One user. |
| Association | Optional. The record the task is about (see What a task can be linked to). |
| Status | Open, In Progress, In Remediation, In Escalation, or Resolved by User. New tasks start as Open. |
| Extras | Optional External Link, Tags, Custom Fields, and Attachments. |
| Sub-tasks | One level of child tasks, each with its own status, assignee, and due date. |
What a task can be linked to
Pick an Association Type, then the record. The types you see depend on what your organization licenses:
| Association type | Notes |
|---|---|
| AI Agent, AI Model, AI Use Case, MCP Server | With AI Governance |
| Asset | A data store, application, or other asset in your inventory |
| Asset Object | Pick the asset first, then one of its objects (a table, bucket, and so on) |
| Assessment, Assessment Project | With Assessments |
| Business Entity, Product, Service | From your data map |
| Cloud Resource | A resource discovered in a connected cloud account |
| Customer, Partner | With Customer or Partner Management |
| Identity | A user or service identity from a connected identity provider |
| Policy Violation | An issue raised by a Policy Center policy |
| Repository | A connected source-code repository |
| Risk | A risk in your Risk Register |
| Vendor | A vendor in your inventory |
A task doesn't have to be linked to anything. Leave Association Type empty, or set it to None, for general work.
Sub-tasks
Sub-tasks break a task into steps. They go one level deep - a sub-task can't have sub-tasks of its own.
- A new sub-task starts with its parent's association, Medium priority, and Open status. Open it to set an assignee, due date, and anything else.
- The parent shows progress as done/total (for example, 2/5 done) in its drawer and in the Sub-tasks column of the list.
- A sub-task's drawer shows Sub-task of its parent at the top, so you can get back to it.
- If you resolve a task that still has open sub-tasks, Relyance asks Resolve with open sub-tasks? first. Click Resolve anyway to go ahead; the sub-tasks keep their own status.
Custom fields
Custom fields on tasks are shared across your organization: a field you add for tasks shows on every task, as a column you can add to the list, and as a filter. Users with edit access can add a field straight from the create dialog or a task's drawer.
The Jira workflow connection
Tasks connect to Jira through the Jira Workflow Connector, the same connector that pushes issues, assessments, and risks:
- Push to Jira. Once a Jira connector is configured, a Push to Jira button appears in the task drawer. Select the Jira connection and click Push. The ticket uses the project, issue type, field mappings, and status mappings from the connector's Issues Configuration, and a Linked Issue link to it appears on the task.
- Tasks on an assessment. A task linked to an assessment that's already in Jira is created one level below the assessment's ticket - for example, a Story under an Epic, or a Sub-task under a Task. Push the assessment first. See Assessment Configuration.
- Two-way sync. If fields are mapped Two-way and the webhook is registered, status changes, edits, and comments made in Jira update the task in Relyance AI. See Webhook Configuration.
If your team tracks work in another tool, put the ticket URL in the task's External Link instead.
The Slack Workflow Connector sends Slack notifications when someone is assigned a task or mentioned in a task comment.
Creating and working tasks
Access and permissions
Tasks follow the Data Mapping Foundation scope, the same scope as Issues and Inventory. See Configuring Scope Based Permissions.
| Permission on Data Mapping Foundation | What the user can do |
|---|---|
| View | See the Tasks list and open tasks |
| Edit | Create and edit tasks and sub-tasks, change status, add custom fields, tags, and attachments, and push tasks to Jira |
When you add a new user from a task's assignee picker, they're given View, Edit, and comment access on that scope so they can work the task.
Create a task
- Go to Act → Tasks and click Create. The Create New Task dialog opens.
- Enter a Title and, optionally, a Description.
- Set the Priority and, optionally, a Due date.
- To link the task, choose an Association Type, then pick the record. For an Asset Object, pick the asset first, then the object.
- Choose an Assignee.
- Under Extras, optionally add an External Link (for example,
jira.example.com/browse/TASK-12;https://is added for you), Tags, Custom Fields, and Attachments. Attachments can be PDF, Word, Excel, PowerPoint, CSV, PNG, JPG, or ZIP files. - Click Create Task. The task opens in its drawer.
You can also click Create New Task on an asset, an asset object, an assessment, or an assessment project. The task is linked to that record for you.
Work a task in its drawer
Click a task in the list to open its drawer. The Overview tab holds:
- Status, Priority, Due Date, and Assignee at the top, plus Push to Jira when a Jira connector is configured.
- The Title and Description, both editable. Click Save after changing the description.
- Associated With - the linked record, which opens in one click. Click the pencil (Edit association) to link the task to a different record, or set the type to None to unlink it.
- Creator - who created the task.
- Extras - the External Link, Tags, and Attachments that are set. Use the + External Link, + Tags, and + Attachments buttons to add the ones that aren't.
- Custom Fields for tasks.
- Sub-tasks - click Add sub-task, type a title, and press Enter. Click a sub-task to open it.
The Status Changes, Comments, and Attachments tabs hold the task's status history, discussion (with @mentions), and files.
Find and organize tasks
The Tasks list is a grid with a filter bar:
- Columns - choose which columns show and drag them into order. Available columns are Associated With, Associated Type, Status, Priority, Sub-tasks, Created, Due, Assignee, External Link, Tags, Creator, and each task custom field. The Task column always shows. By default you see Associated With, Associated Type, Status, Priority, Sub-tasks, Created, Due, and Assignee.
- Sub-task filter - show Sub-tasks only or Top-level tasks only. Leave it unset to see both. Tasks and sub-tasks have different icons in the list.
- Filters for status, priority, assignee, and your task custom fields, plus Group By (none by default).
- Saved views - save a combination of columns, filters, and grouping to come back to.
Configuration checklist
- Confirm the right users have Edit on the Data Mapping Foundation scope.
- Add the task custom fields your team needs (for example, control ID or remediation type).
- Configure the Jira Workflow Connector if your team works in Jira, and register the webhook if you want two-way sync.
- Connect the Slack Workflow Connector for assignment and mention notifications.
- Set up and save the Tasks list views your team uses - for example, open tasks by assignee, or tasks linked to risks.
FAQs
Q: Does every task need to be linked to something?
A: No. The association is optional. If you choose an Association Type, you must also pick the record, or the dialog shows Task source is required. You can add, change, or remove the association later from the task's drawer.
Q: Can a sub-task have its own sub-tasks?
A: No. Sub-tasks go one level deep. The Add sub-task button only appears on top-level tasks.
Q: What happens to sub-tasks when I resolve the parent?
A: Nothing changes on the sub-tasks. If any are still open, Relyance asks you to confirm with Resolve anyway, and the sub-tasks keep their status.
Q: Are sub-tasks pushed to Jira as Jira sub-tasks?
A: Each task, including a sub-task, is pushed on its own with Push to Jira, using the connector's Issues Configuration. Only tasks linked to an assessment that's already in Jira are created as children of another Jira ticket.
Q: Can I set a due date in the past?
A: No. The due date can be today or later.
Q: Why don't I see AI Agent, Assessment, Customer, or Partner as an association type?
A: Those types only appear when your organization licenses the matching module - AI Governance, Assessments, Customer Management, or Partner Management.
Q: Can I use Markdown in a task description?
A: Yes. Text pasted into the description that reads as Markdown - headings, lists, bold, links, code - is formatted as you paste it. Tasks created by the Relyance AI assistant render their Markdown descriptions the same way.
Q: How are tasks different from issues?
A: Issues are raised by Relyance - from scans, policies, and other system checks - and appear under Act → Issues. Tasks are created by your team, either directly or from a record, and appear under Act → Tasks. A task can be linked to a policy violation so the remediation work is tracked alongside the issue.