Statuses don't have to be locked system wide to appear on a specific team's agile board | Community
Skip to main content
New Participant
March 10, 2017
Approved

Statuses don't have to be locked system wide to appear on a specific team's agile board

  • March 10, 2017
  • 25 replies
  • 3499 views

Right now I am having to lock all group statuses at the system level to allow them to appear on a teams agile board. We have 20+ task statuses in the system right now and growing. And they are not all relevant to all users (ie we do building construction and software custom development each with wildly different status progressions)

25 replies

Kelly_Wehrmann
New Participant
July 29, 2019

This is definitely an oversight in the product no only with Kanban but also Approval Processes. Visited with different Workfront resources at Leap to discuss. Also have tickets opened with our ASE in support and looped in our CSM and Sales managers. I'd really like to see this changed to be more of an immediate fix all the way around.

New Participant
July 12, 2019

Good to see this thread - I have heard nothing from WF support on this and have been struggling with this for days now. It is imperative we have this functionality, or we end up with a long list of statuses and the wild west of choices avaiaible....this is absolutely not logical...

AileenTa
New Participant
July 10, 2019

This is a similar request: https://experience.workfront.com/s/idea/0870z000000PSoUAAW/detail


One of our teams just moved to the Kanban view and we were distressed to learn that their swim lanes will need to be system wide task statuses. How can Workfront become a "global" system of record when it continues to insist that all groups in a company work in the exact same manner. All systems should be able to be assigned to just groups or teams.

New Participant
June 28, 2019

All, this is an idea we are currently investigating. We plan to solve this problem by adding group statuses to the agile board.

New Participant
June 12, 2019

@Gevorg, is there anything related to statuses on the Agile roadmap for the next 12 months? This seems really odd for things after LEAP 2018 to be moving forward in a positive way for the Agile side of Workfront and now it seems to have just stopped and lost all forward momentum.

New Participant
May 31, 2019

Hi everyone,

Thanks for upvoting the idea!

It looks very promising, however I'm marking it as "Not Planned" since it is not on the roadmap for the coming 12 months.

At the same time, I would kindly ask you to continue adding your use cases under this idea so that we can consider those when we are back to this idea.

Thanks,

JennChing
New Participant
January 19, 2019

Thanks James Bender! I tried the workaround in my Sandbox environment & it works. :)

New Participant
January 3, 2019
New Participant
November 29, 2018

Useful upgrade...

New Participant
November 29, 2018

We could REALLY use this too!!!