Using Plan Mode

Is there anyway I can see my sub-task on Plan mode?

I wanna add task while I'm planning my sprint, since in my case, it's more accurate to add all these task while planning.

Why there are no sub-tasks in left column?

Could it be in settings?

I would be nice to customize viewable columns in this mode.

It keeps giving me errors telling me i don't have the permissions to edit or start this sprint. Anyone have any ideas as to how to fix this?

Hi,

thank you for the new approach with the Rapid Board, we're really looking forward to using it.

But, we have more then 1500 Issues in the Backlog and the planning mode makes it nearly impossible - or I didn't get it 

I moved all issues above the sprint marker (which appeared right in the middle of the backlog, why?!) to the top with (send to top). Then I tried to use quick filters to find the issues we want to have in the next Sprint. I found the issues, and "sent them to  top". When I now disable the quickfilter the sprint marker is again at the middle of the backlog having hundreds of issues included.

How is that supposed to work? Do I have a wrong setup? (Ranking is enabled) 

Thank you very much for your help

Andreas

After I close a sprint, how do I move/re-prioritize the unfinished items to the next print?

I would expect that the Quick Filters 'exclude' certain issues from the selection you make from the backlog.

i.e: i have 100 issues in the backlog, and exclude the first 20 by a quick filter.

Then, i select the first 10. But, the sprint marker gives me back 30, so the selection includes the first 20.

I have several products, for each product i have create different project. I'd like to have separate backlog and sprint for each product. Can i do it with Green Hopper?

Planning board is a great idea but suffers from several issues...

1. The estimated times of sub tasks are not cumulated in stories (they do in normal issue navigator mode) - deal breaker since we estimate sub-task not stories
2. The board cannot be configured to show more columns - deal breaker since usually we want to see during planning other factors like cost (calculated custom field), and other custom fields
3. It would be great if we could print this plan out
4. It would also be great if the display of sub-tasks could be toggled (like on Planning Board, but subtasks should appear below their story not in random order... )
5. Placing separator lines (e.g. for miletones) would also be welcomed

Hi,

I have a problem with the Planning Board. My filter for the Planning Board said that I have more than 1000 issues. But If I look to the Planning Board I found only round about 100. That is not enough. How can I configure the Board for more entries? How can I edit the rank? Or how can I modify the filter, so that I can see all the issues on the Board?

Thanks.

Daniel

I have a question for   greenhopper v 5.10 .  I have several products, for each product i have create 4 or 5 scrum  teams,how can i  use plan board to  play more than one sprint for each scrum team? 

thanks.

Hello.

There is a big problem with this new approach. We use a lot technical tasks, they are more accurate to us... But it doesn't appear in the planning board for me to drag. Can you guys change this?

Thanks

I'd like Plan mode to show bugs, but no matter how i configure the filter bugs don't appear.   What am i missing?

We are primarily in maintenance mode and want to be able to release work that is complete at any time which lends itself to flow.

However we find ourselves asking if the rigid definition of Kanban in Greenhopper is really accurate. Does it make sense to remove the Plan operation from a Kanban board?

You state the To Do column is prioritized for Kanban team and the team works through that list in order. It seems that there still needs to be prioritization of that list and prioritizing is the act of planning.  A product owner should be able to ask questions and may de/re-prioritize any task in To Do. Once it has been moved to the In Progress column the ship has sailed for that task. But if it is in that To Do column it is open to being subjected to the prioritization process. Many attributes of an issue can factor into that prioritization such as the amount of work it would take to complete. We capture this with other teams in terms of Story Points. As we look at tasks that are dragged into the To Do column we'd like to be able associate Story Points with them so the product owner can make informed decisions around prioritization.

It would be useful for us if there was the ability to select the Plan mode so we can have a discussion around the issues in the To Do list and add story points, comments and drag to re-arrange and prioritize.

Maybe this is seen as a hybrid between the Scrum and Kanban models but if the work flowing in to the Kanban team can change at any time (the To Do list is always able to be re-ordered) then it seems like a Plan mode would be valuable for interacting with just the To Do list.

Thoughts? Are we mistaken in the way we want to use Kanban? 

When clicking on "Add Sprint", there's no way to change the Sprint designation (name/number). We already have a sprint going on (Sprint 2), and the "Add Sprint", adds a new sprint with the name "Upcoming Sprint 1". Is there a way to change the sprint name, before the sprint actually starts?

Thank you.

What are the restrictions associated with the "Add Sprint" button?  I would like to have some other people Add Sprints when they think they are done pre-planning what is on the rapid board.  What do I have to cnfigure to allow, or restrict, access to this button?

tia

I'd also like to see the ability to configure some columns in the Plan board.  For example in our planning phase we have statuses for Open, In Backlog, Grooming - all before we mark a story 'Ready for Development'.  It would be really nice to be able to slide stories around the Plan board to get them into 'Ready for Development'.  Then we would be able to create the Sprint, and move to the Work board to manage the rest of the workflow.

Any thoughts?

I agree with anonymous' input

I can see that we have a limit of 400 issues in plan mode ? How can I get my 600 issues ? :s

Maybe i´m a little bit confused, but is there no option to edit/see directly the "due date" in the planning board? Actually i can only see "Created" and "Updated" date...

As a product owner I want to rearrange entire sprints. 

As I could not figure out if that was possible in v6.0.2-rc1 (OnDemand) I posted a question on Atlassian Answers: How can I rearrange (sort) entire sprints in Rapid Board Plan Mode? 

We often have a huge backlog. When we add a new story it automatically goes to the bottom. If we need t work on it right away, it requires us to drag it all the way to the top which can literally take over a minute or two to do so. It would be nice to have a "move to top" button. (like Netflix. =)

I have a silly question.

I have not had extensive time or really played with Greenhopper too much as we are rolling out JIRA in my organization and decided to use Greenhopper. With 6.0, the previous boards have been called Classic and new users or projects are directed to the new Boards (previously Rapid Board).  In the Classic board view, agile users could create and nest versions, components and create issues (cards) all from the planning board.  The new boards do not allow you to do any of this.

Is the direction with Greenhopper to have users go back to creating and managing work in the standard JIRA perspective and then switch to agile to rank, and create sprints, and subtasks? 

I ask because with the designation of Classic I assume at some point it will go away so before I upgrade to 6.x I need to make sure I have answers for my users who have jumped on to using Greenhopper for the past few months without us officially rolling it out and who have grown accustomed to performing all these tasks in the planning board view.

I appreciate any response and if I just overlooked something, please correct me. Otherwise, I will continue reading up on the new features.

Still not possible to display more than 400 issues ? :s I have more than 600 And I would like to display everything....

Is there a way to search (and ultimately export) stories that are slated for a future sprint(s)?

We have made a lot of sprints, and have began working on the project. We missed some work that must be done and therefore we created a new sprint at the end of the list. But this newly created sprint we would like to move up in the sprint hierarchy. Is there any "easy" way to do this?

has anyone found a way to get tasks to appear in the backlog?  We have a number of tasks that aren't truly related to a story, but yet represent work that needs to be done during a sprint.  The tasks have been defined and appear in my backlog query/filter (when run outside the Planning mode) but they don't appear in the backlog when in the Planning Mode.  Do I need to create pseudo stories just to get the tasks to show up in the Planning mode? 

I am planning sprints for two separate teams on the same project.  Each have distinct skill sets and I've set filters based upon story labels to enable me to split them.  However when I remove the filters, each teams iteration fills up with stories from the other teams iteration, even though both iterations have different names (i.e. team name: sprint number).  Is this because they share the same project? I'm concerned that when a sprint is started both teams will be looking at the same stories which kind of defeats the object of planning the stories out between the two teams based upon skills!

In the classic boards it was possible to plan a release comprised of multiple sprints. Is this possible now? I can't find it in the documentation. 

1. Release 1
   
   1. sprint 1
   2. sprint 2
   3. sprint 3
2. Release 2
   
   1. Sprint 4
   2. Sprint 5

This was useful in many ways;

For business owners it was possible to generate a backlog of the entire release

For QA and BAs it was possible to generate a report of Release X stories and bugs. 

Hello - Is there any way to configure Plan mode view? Issue ID and Summary get displayed by default. I also would like to see created date and couple other columns in this new view.

Is there a way to view workload on developers? this is crucial when performing sprint planning. Or at least see a simple and clean list of each developer, and his/her assigned stories and tasks.

How do you complete a sprint that was already started? I don't see any options. 

It looks like many people are asking for subtasks to appear in the backlog, but nobody from Atlassian has commented.  What gives?  Is this clearly requested feature going to be added in?  

If you, as we, have storyes that can span over more than one Sprint and Subtasks are the ones that are assignet to sprints, then this is a must have feature to be able to see subtasks and the their parrent on the left side

One team that uses the Rapid Board in my company is complaining about the upcoming sprint marker; according to them, the marker is moving (downwards) without any user interaction. I'm trying to recreate this behaviour, and i'm looking for possible scenarios.
Is there anyone else experiencing these symptons? From the back of my head, i can't think of many situations that explain the 'automatic movement'.

Well, they drag the upcoming sprint marker so that they include 35/40 issues in the upcoming sprint.
The next time when they open the backlog 200+ issues can be included in the upcoming sprint, and nobody seems to have done that.

The following features would be very welcomed:

• Support for JQL in quick search to filter the backlog 
• Possibility to customize which fields are displayed in each row of the backlog - currently only the Summary is displayed, however having additional fileds there (like Due Date, assignee / user fileds, custom fields) would significantly aid the planning process.

I need to create a weekly report of the whole backlog, meaning a view of all sprints and their stories currently planned and (underneath) the rest of the backlog. Is their a way to to create such report or print this?

We tried to use the previous version of JIRA and GH to plan a sprint, but had to fall back to Classic.  We have tried again today (JIRA 5.2.5/GH 6.2.1), but again find it necessary to switch back to Classic. Here is how we work:

• We do round 1 planning of a sprint on Tuesday afternoon. Some stories may have sub-tasks, others won't. Some sub-tasks are assigned, other aren't. And we do story point assignment and discuss who is doing what. Many stories will have sub-tasks divided across multiple developers/QAs.
• Wednesday morning everyone creates or updates existing sub-tasks.
• Wednesday afternoon we all review the work, ensure everything is assigned, ensure nobody is overloaded...and start the sprint.

And here's why we're switching back to classic (again):

• I set up QuickFilters for all the team members so that I could see how many hours was assigned to each in the sprint being planned (to make sure nobody was overbooked on hours). Many of our stories are split across multiple developers. If the story isn't owned by the person matched by the QuickFilter, then you see 0 stories, yet 1w1d2h (for example). So you know that person has work, but you cannot see what the work is.  That is a HUGE issue. I need to be able to every thing assigned to a specific person during the sprint being planned.
• I also set up a QuickFilter to see what work (tasks, sub-tasks) are unassigned (to make sure we're not forgetting anything). The sprint view in plan mode showed nothing was unassigned. But we did have several sub-tasks unassigned...but since the parent story for the sub-tasks was assigned, I got 0 stories matching the QuickFilter.  Same issue as above, with a different face.

If I'm doing something wrong, I'd love to hear it. Otherwise, I find it unusable.

I can understand David´s concerns about the usage as we´re facing more or less the same problems!

In my opinion a small feature would ease up the situation a lot: Make upcoming sprints searchable via issue filter! In this case you can use all of the reporting stuff like pie charts etc., this should answer all these questions. This feature has been requested several times i think, what is the actual status?

as per some of the other feedback - just tried using the new board and am really struggling without being able to see my subtasks - and drag them into sprints indepedendent of their parent tasks - in plan view

If i am missing something let me know but i do not see any subtasks in plan view - other than by clicking on parent issue - but I need to be able to drag a subtask into a sprint

Is it poosible to see both business value and story point in the overview page of plan mode?

hey guys can you please help, I'm doing a product backlog about "daily operations- bookings and payments"

I have a question about the Backlog filter. When in Plan mode, the backlog shows a number of issues. But displaying the same filter in edit mode brings totally different number of issues. Usually a lot more. Here is the thing: I have a hard time figuring out what it filters out. I noticed some issues which are "In Progress" are in the Backlog. This does not make sense at all.

Please advise...thank you.

Not sure if this is why, but If you have issues with "resolution != empty" they will not show up in the backlog filter, although they will be in the query.

Is there a way to configure what issues show up in the product backlog? For instance I have my filter set up to list issues of all resolution types (even resolved ones, please don't ask me why), but the backlog in plan mode automatically rejects those issues.

I understand that the recommendation is to move to using an Epic->Story->Sub-task hierarchy. Currently our Product Management team logs 'Improvement' or 'New Feature' issues in JIRA. What is the recommended way to use 'Improvement' and 'New Feature' issues in the new model? (Previously we just created sub-tasks of these, and once all the sub-tasks were complete the Improvement/New Feature was marked complete). Would you expect the Product Management team to start logging Epics instead of 'New Feature' issues? Or should the Improvement/New Feature be added to a new Epic created at the time the development team starts to work on them?

First things first, I'm new at using JIRA!

Now, my question.  I'm looking at the possibility to create sprints with issues from 2 projects.  Can this be done, and if so, how?

TL;DR all the comments... Got kinda stuck reading folks abusing the sub-task.

Sorry, Atlassian, but I would never promote breaking stories into sub-tasks.

To break a story (issue) down into implementable chunks

That might get newbies to thinking they decompose a story (feature) into something abhorrent like this:

• Support Users with Middle Names
  • Add database column for middle name
  • Add middle name to User class, make sure it is allowed to be empty
  • Add middle name field to the User profile page
  • Stab yourself with a hot fork

I use sub-tasks on a rare occasion when a developer wants to add some granularity to how a feature is going to be completed.

Instead, I recommend decomposing stories (a.k.a., feature, use case, requirement) into actionable, smaller features.

Or, if it is an infrastructure type task, it is not uncommon for folks to break that into 10 sub-tasks to do something that might stretch over days, be done by different people, and you want to keep an eye on both where the overall task is at, who is doing what, and which sub-task(s) are currently unfinished.