Subscribe To Our Newsletter
Join our community of thousands of readers.
Table of Contents
Note: This update is for zipBoard enterprise users. If you arenāt one but would like to try the new feature then reach out to us at [email protected].
A task jumps between various statuses before completion. What status you assign a task and how long it stays there depends on you and your teamās workflow. This is why we do not want your team to be limited to fixed task statuses. Which can be limiting, and not exactly reflecting your teamās internal task workflow. The answer to this is task statuses you can customize based on YOUR need.
But what if youāve integrated zipBoard with Jira or Wrike? This would surely lead to inconsistencies between the two apps. To deal with this, weāre also introducing a feature that lets you map your zipBoard statuses with your Jira/Wrike statuses and vice versa. Letās get straight into it!
In a hurry? Hereās a short clip to explain how you can create custom task statuses now.
So, whatās new?
Letās check out the 4 key updates.
Customize your task statuses
The meatiest update in this new push, now you can create custom task statuses to fit your workflow. Say bye to putting square pegs in round holes.š
You can do this from the org level under āManage Orgā. There are two ways you can go about customizing your task statuses.
1. Change the existing status names.
2. Create a completely new status.
This will now start reflecting on all your tasks, right away!
Learn more about customizing task statuses. ā”
Map statuses to integrations
Once you access a project after adding a new status, you will see a prompt asking you to map the new status with your Jira or Wrike integrations. (You will not see this if youāve not integrated zipBoard with either.) This step ensures that you have consistency throughout different apps.
The mapping takes place in five stages.
- Choose the project that you want to map.
- Map the zipBoard task type.
- Map your zipBoard task statuses to the integration. If you have custom statuses on Jira, they will be displayed here. This means that you can create parallel statuses.
- Map your Jira/Wrike status to your zipBoard ones. This is necessary so that if you change the status in Jira/Wrike, it will be reflected in your zipBoard acc. Consider this as reverse mapping. This might sound a bit confusing at first, but weāve got you covered. Click here to get a step-by-step guide for this update.ā”
- Lastly, a brief overview of the mapping selection is displayed. With arrows pointing in the direction of mapping.
Learn more about mapping task statuses to integrations. ā”
Delete Task Statuses
Customization doesnāt truly make sense without having the ability to delete unnecessary/redundant statuses. We donāt want to clutter your statuses.š
You will see that four statuses are checkmarked. These are the minimum number of statuses you must have and cannot be deleted. These statuses can however be edited as you like.
Once a status is deleted, a pop-up will appear asking you to replace the corresponding tasks with this status with an existing one. This is to ensure that no tasks are left statusless. This also makes sure your integrations automatically map them with the replaced statuses.
Learn more about deleting task statuses. ā”
Visualize changes in reports
Finally, managers and admins use reporting to get a better understanding of their tasks, feedback and the overall project. So, weāve made sure that the changes made to the statuses are reflected in the reports in real time.
New features, same great product
In our continued effort to make zipBoard the most reliable content review tool, relevant to our users, weāve added these features. If you have any questions or issues with these updates, feel free to reach out to us [email protected] or book a free demo.
Note: This update is for zipBoard enterprise users. If you arenāt one but would like to try the new feature then reach out to us at [email protected].
Integrations
Follow Us:
Ā©ļø Copyright 2022 zipBoard Tech. All rights reserved.