In Progress & Waiting for Approval statuses
complete
B
Barbara
- Enable the ability to create and manage custom statusesfor feedback in Marker.io.
- Allow users to map these custom statuses to statuses in connected tools (e.g., Jira, ClickUp, GitHub).
Use Case
- Greater Flexibility: Users can better match their workflows by defining custom statuses (e.g., "In Progress," "Pending Client Response," "In Review").
- Better Visibility: Clients and team members can see more detailed task progress directly in Marker.io.
- Workflow Mapping: Sync multiple statuses from external tools like Jira to Marker.io for status updates (e.g., map Jira statuses like "In QA" or "Ready for Staging" to Marker.io custom statuses).
- Guest Collaboration: Allow guests to see more granular task statuses, keeping them informed about ongoing progress.
Benefits
- Improved Communication: Teams and clients can understand the status of a task at a glance, ensuring everyone stays on the same page.
- Better Tracking: Project managers can easily distinguish between tasks needing attention versus those waiting on client input or external factors.
- Integration Compatibility: By supporting status mapping with integrations, teams can align Marker.io with their existing workflows.
Log In
Emile-Victor Portenart
marked this post as
complete
We're launching 2 new issue statuses: In Progress and Waiting for Approval.
Teams can now move issues through a complete lifecycle instead of the binary Open/Resolved workflow and see what's being worked on and what needs review.
Learn more here -> https://feedback.marker.io/changelog/in-progress-and-waiting-for-approval-statuses
--
This post has been renamed to match the initial release covering 90% of use cases. For anyone who need more granularity in statuses, please upvote this post https://feedback.marker.io/admin/feedback/feature-request/p/custom-statuses-1
Emile-Victor Portenart
marked this post as
complete
We're launching 2 new issue statuses: In Progress and Waiting for Approval.
Teams can now move issues through a complete lifecycle instead of the binary Open/Resolved workflow and see what's being worked on and what needs review.
Learn more here -> https://feedback.marker.io/changelog/in-progress-and-waiting-for-approval-statuses
--
This post has been renamed to match the initial release covering 90% of use cases. For anyone who need more granularity in statuses, please upvote this post https://feedback.marker.io/admin/feedback/feature-request/p/custom-statuses-1
OuterBox
Great call out. This would be a very valuable enhancement.
Emile-Victor Portenart
marked this post as
in progress
E
Elizabeth Nixon
I love this enhancement! But I'll cry if it's not available to free users :)
Emile-Victor Portenart
marked this post as
planned
Gary Gaspar
marked this post as
under review
Lance Unrau
This would definitely help a lot even without the ability to map statuses across platforms. I have tasks I'd like to set aside without resolving them, as I'm waiting for client feedback, the site to launch, or various other reasons. Assigning tasks to users would also be helpful.
Iris Carde
This feature would benefit projects where we've integrated with DevOps and use custom States. It'll assist with communicating with our clients when items are pending feedback, etc.
Joe Scanlon
Merged in a post:
Status auto-update Override
Michal Bednarczyk
Ability to disconnect a certain issue from Status auto-update with Asana. While i love status auto-update in general, there are occasional issues where i want to mark it complete and have the client see it's marked complete while keeping it open internally in my PM system to work through any final bits.
Joe Scanlon
Merged in a post:
Status changes from Teamwork
Travis Warlick
Request: Similar to the integration with ClickUp, allow movement of a Teamwork task to particular Teamwork board columns to trigger resolution of Marker.io feedback.
Background: Currently, Marker.io items are resolved when the task in Teamwork is marked as complete. This presents with some process challenges because our definition of "complete" in Teamwork includes several steps after the point when we need to communicate that feedback is resolved with respect to Marker.io. This is because Teamwork locks several aspects of tasks once it is complete, so the very final step in our process for a given task is for the project manager to mark the task as complete. We use boards in Teamwork to work around this. For example, our board columns Client Review, Ready to Deliver, and Delivered are the ones which would be more appropriate for which to trigger the Marker.io feedback status change to resolved.
Load More
→