Release Notes: Grid Behaviours - v2.5
Release Date: January 4th, 2025
This release document provides a detailed overview of the new Grid Behaviours Feature, outlining its purpose, functionality, and key benefits.
It aims to help users understand how the feature facilitates editable and read-only access management within grids. It includes step-by-step instructions for using the feature, and highlights any technical dependencies or requirements.
By providing this information, the document ensures smooth adoption and integration of the Grid Behaviours Feature into existing workflows.
Overview
Idea: Grid Behaviours feature enables restrictions on editing grid content based on user group and issue status. It simplifies access management within grids by defining editable and read-only permissions.
🎯 Goal: The primary goal is to provide a streamlined workflow and interface for configuring and applying grid editing restrictions, ensuring flexible yet controlled access to grid content.
Key Features
Grid Configuration UI Update
A new "Grid Behaviours" tab is added to the grid configuration interface for managing grid behaviours.
Configure New Grid Behaviours
A button labelled "Add Grid Behaviours" allows users to create and configure grid behaviours. Clicking opens a form-based popup.
Edit Grid Behaviours Configuration
Users can edit the existing grid behaviours configuration by clicking “Edit” button on each one.
Delete Grid Behaviours
Users can delete the existing grid behaviours by clicking “Delete” button on each one.
Apply Grid Behaviours to Grids
Apply access for a user to a grid on an issue based on:
Attribute (Editable/Read-only)
Condition (Issue Status)
Restriction (Users/Groups/Everyone)
Audit Log Monitoring
Tracks grid behaviour logs with a focus on conflicts and errors. It displays:
Failed/conflict logs.
A success count (e.g., "Number of success runs: 61").
Automatic cleanup of logs older than 24 hours (daily at 00:00 UTC).
Instructions for Use
Add Grid Behaviour
Step 1: Accessing Grid Behaviours
Navigate to the grid configuration interface.
Select the "Grid Behaviours" tab.
Step 2: Adding a New Behaviour
Click "Add Grid Behaviours" button to add your first grid behaviour.
When you already have grid behaviours, click “Add” button to add a new grid behaviour.
Step 3: Configuring the Behaviour
Name Input: Enter your grid behaviour’s name
Element Input: Pre-selected as "Grid" (default) and you can not change it.
Attribute Input: Choose between "Editable" or "Read-only".
Editable: Users who have this access can read and edit the grid.
Read-only: Users who have this access can read and can not edit the grid.
Condition Input: Select "Issue Status".
Issue Status Input: Select applicable statuses (e.g., "Open", "Closed").
You can select multiple issue statuses for each behaviour.
6. Restriction Input: Select "Everybody", specific "Users", or specific "Groups".
Logic to Apply Behaviours:
Behaviours enforce grid access permissions based on priority:
Individual Users > Groups > Everyone.
If a user is both individually editable and read-only as part of a group, the individual setting overrides the group restriction and everyone restriction also.
Conflicts are flagged when overlapping rules exist, with earlier-created behaviours taking precedence.
If two grid behaviours in a grid have the same restriction and condition, prioritize the earlier-created grid behaviour.
6.1 Everybody: Apply the access of this grid behaviour to all users in the current organization.
6.2 Users: Apply the access of this grid behaviour to all the selected users.
You can select multiple users.
You can type characters in the “Select Users” field to search for users.
Especially, you can type “@” in the “Select Users” field to show all the active users in your organization as selections in the dropdown list.
6.3 Groups: Apply the access of this grid behaviour to all users in the selected groups.
You can select multiple groups.
You can type characters in the “Select Groups” field to search for groups.
Click "Save" to save the grid behaviour configuration.
After saving, the new grid behaviour will be displayed on the Behaviours List.
Monitoring Behaviour Logs
Open the "Recent Failed Audit Logs" from the "Grid Behaviours" tab by clicking
button.
Review conflict and error logs.
Feedback and Support
For more information, visit our Support Portal here.
Conclusion
The Grid Behaviours feature empowers administrators to control grid content access efficiently by defining restrictions based on user roles and issue statuses. With intuitive configuration options and robust monitoring via the Audit Log, this feature ensures that editing permissions align with organizational requirements while resolving conflicts through a clear prioritization hierarchy.
By leveraging this feature, users can streamline grid management while maintaining precise control over who can edit content and under what circumstances. This functionality is designed to reduce complexity and enhance productivity within your organization. We encourage users to explore the "Grid Behaviours" tab and customize access rules to suit their unique workflows. If you encounter any challenges or have feedback, our support team is available to assist and improve your experience further.