Display Card Estimates in
Some teams prefer to work out estimates for work items in ‘Story points’ while others in ‘Days’. In SwiftEASe, an account can define one Unit of Measurement (UoM) for estimation across boards.
As an administrator, once you define the UoM, it will be used to capture the estimated effort when adding cards on Work Boards and adding the PI capacity.
To define the UoM for estimation:
- Click the Admin Policy icon on the Settings page.
- Enter the UoM in ‘Display Card Estimates in’ box, for example, Days or Points. Note that the label should not exceed six characters.
On editing the UoM, the estimates label changes to the new label, (for example, ‘Estimates (Points)’ but the units captured will be the same as earlier and not changed or converted.
Note: Interpret Estimates, To-Do Estimates, Actual Effort, Remaining Effort and Burndown chart in the PI and sprints charts according to the UOM defined here.
Show Live Updates on Board Refresh Only
You can get instant updates on any changes the team members make to the cards on the board by regular refresh, by default. This is a very useful feature for a distributed team to be in sync. When you have your app open but are working on some other app, on returning to the board, the board highlights the updated cards one by one. This feature is optional and can be disabled by selecting the preference for your enterprise. You can choose to refresh the board manually and see the final updates as and when required.
To disable automatic Board Refresh, perform the following steps:
- Go to Admin >> Settings and click the Admin Policy icon.
- Select the ‘Show Live Updates on Board Refresh only’ option.
Note that the changes will take effect on restarting the session.
Automatic Board Refresh can be enabled again by clearing the selection.
Note that changes refer to the updates to the card attributes displaying in the Add Card window, such as Title, Description, Priority, etc. The changes made in the Detail view of a card is not reflected in the Board Refresh. The cards highlighted on the board indicate that they were modified.
Enable Card Tags
In the Admin > Settings >Admin Policy view, select the ‘Enable card Tags’ policy to enable tags so that team members on boards can add and update tags/labels for cards. These tags can be used to search cards across boards and filter the board to focus on specific cards.
Tagging can be a great way to associate cards with a release, sub-tasks to a story, feature, or board, etc. You can view the Tag Cloud metric, which gives you a collocated visual view to understand what are the key drivers of your board. Hence, if you assign tags to a card such as customers, technologies, specific themes, etc., you can analyze the biggest drivers for your deliverables.
Default Date Format
You can define the default Date Format at the enterprise level, and all the new users will have that date format as default when updating any date field.
Note: Although new users will have the selected date format as default, they can always change it by modifying their Profile Summary.
Show Card Type-wise Progress on Parent Card
This policy will let you view the progress of the parent cards based on the card types of its child cards.
Show Basic Details of Card in Hierarchy and PI to Non Team Member
The user, who is not a team member on a Work Board, can view the ID, title, board name and current column of a card of that board, displayed in the Linked Cards section, provided the Show Basic Details of Card in Hierarchy and Release/Iteration to Non Team Member checkbox is selected on the Admin > Settings > Admin Policy page.
Apply Password Policy (minimum 7 characters):
Password policies are required to enhance the account security by encouraging users to employ strong passwords and use them properly.
To enable the password policy:
- Go to Admin >> Settings
- Click the Admin Policy icon on the side toolbar at the left.
- Select the Apply Password Policy checkbox.
- Select a policy from the drop-down.
- It will save the settings automatically.
Note 1: You need to restart the session to apply the changes.
Note 2: If the above password policy is not applied, by default minimum 7 characters password of any combination is applicable. Same will be reflected on the change password screen.
Updating Cards in Done Column
You can restrict the access of updating the cards or performing certain operations on cards in the Done column. If you enable the Allow editing of cards in Done column policy, then only the Board Admin and the Manager will have the access to update the cards or perform card actions in the Done column.
Allow Deletion of Board to Admin Only
Only the Admin and Manager will be allowed to Delete Boards. To prevent any accidental deletion of the Board, the Board deletion facility is kept available only on the Board Profile page only. If we enable this policy, it gives control on the Board Deletion only to Admin.
To enable the Allow Deletion Of Board To Admin Only, perform the following steps:
- Go to Admin >> Settings
- Click the Admin Policy icon on the Side toolbar at the left.
- Select the checkbox for the Allow Deletion Of Board To Admin Only policy.
Show ID in the Card Title of the External Work Requests
Enabling this Admin policy Show ID in the Card Title of the External Work Requests prepends the card ID to the title of your cards that are created by submitting the External Work Request form, resulting in faster search. To know more about External Work Request, see this page.
Apply Concurrent Data Update Policy
Many a time, multiple users working on the same card may attempt to update the card simultaneously. To control the most recent version of the card, use this policy.
Using this policy, you can select the option either to Restrict the user from saving the changes in a card if it has been simultaneously updated and saved by another user, or just Warn the user about the changes done by another user. Alternatively, you can also disable this policy by selecting the None option.
Do Not Rollup Child Card Estimate to Parent Card
If this policy is not enabled, the Estimate Points of the child cards gets aggregated and rolled up to its immediate parent card automatically. So, the Estimate field in the child cards are editable, but the same is read-only for the parent card.
Using this policy, you can add or edit the Estimate points both at child and parent level. Moreover, when enabled, the Estimate points of the child cards do not get rolled up to the parent card estimate field automatically.