nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Boards and New Statuses

Sheila Shah

Hi - I'm using cloud. I created a new worflow status called Proposed. When a new issue is created, it defaults to the Proposed status (instead of planned). Approvers must approve the proposed issue before planning and dev can start. After it has been approved, the status updates to Planned. I'm in the planned mode of a board I created. I don't see any issues in the Proposed status displaying. I verified the statuses were mapped: I went to Work mode and added a new column called wish list, where the Proposed status is mapped to this Wishlist column. Any idea?? Ideally, in planned mode I want to see a separate section (below backlog) for all proposed issues. Is that possible??

Accepted answers

Nic Brough -Adaptavist-

IT sounds like you have not told it that "proposed" should be appearing in the right column, or that you have a board filter that is based on status and isn't including the issues.

Have a look at those two first.

All comments

Nic Brough -Adaptavist-

IT sounds like you have not told it that "proposed" should be appearing in the right column, or that you have a board filter that is based on status and isn't including the issues.

Have a look at those two first.

Sheila Shah

Thanks for quick response. On to my second question. Is it possiblefor me to create a separate section (called wishlist) on the Planned mode below backlog for all issues with status=proposed. Attached is a screenshot. The idea is that my manager wants to be able to view new issues created (proposed) and approve/deny them. He'd like to see a consolidated list on a board/dashboard and approve/deny them there. Not sure if that's possible. f you have another alternatives, we are open.

Nic Brough -Adaptavist-

No, that's not really what sprint planning is for. It would be better to move the approvals into the workflow and then build your board with either a pair of initial columns (new and approved) or change your board filter so that it doesn't have the unapproved issues in it.

I'd lean towards the second, because you can keep it really simple - create a filter for "not approved" stick it on dashboards for your manager and then create a Kanban board for them to approve/deny stuff before your development teams get to planning!

The planning board is about prioritising, not deciding whether something should be done.

Steven F Behnke

Good explanation of the tools Nic!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud