Creating a Sprint

I am using GH 6.0.3 rapid boards.  I created the rapid boards and can successfully Add, Start and Edit Sprints. The rapid boards are one project per rapid board.   Other users have Administer Projects permissions for the project, but cannot add, start or edit sprints in the rapid board for their project.   Am I missing something?   Can those with Administer Projects permissions for the project being used on a board add, edit and start sprints?  

Adding to the previous comment - who is allowed to create new sprints in GH (6.0.3), what permissions / role he should possess?

Upd - just read the comment on the page in disclaimer. Does it mean only project administrator can do it, but project manager can't? Sounds strange

I would like my sprint to be part of a version. I created a product version called "3.2", and I want all my coming sprints to be part of this 3.2. How should I do?

Hi

I would like to add a sprint goal to my sprint so the team can refer back to that goal to ensure they are on track. How can I do that?

I have a release plan ... and 3 sprints in this release. I also have some process tasks that i execute in the end of the release.
In classic version i was avle to put an version inside other version, how can i do that in greenhopper 6 ?

In creating a sprint, it looks like I have to put the entire user story into a sprint.  Is that correct?  Can I put sub-tasks from the same user story into separate sprints?  Or do I need to create my user stories so that they fit within the sprint timeframe?  If so, what happens when a sub-task from a user story needs to move into the next sprint?  Should I move the entire story (or create a new story for the remaining tasks, depending on how I want to track the time)? 

Thanks!

In my experience, you can not put user story partially into the sprint. You can only put it as a whole, and if not all sub-tasks were done within the sprint, you would need to return whole user story to backlog. As an alternative, you can create a new story for remaining tasks as you wrote, and move sub-tasks to the new story (which isn't very convenient).

The idea behind this is probably that user stories in Scrum should be small enough so you don't break them into further pieces. It's a guideline that you should make stories small and complete them entirely ("done") within the sprint. Otherwise, if sroty is half-done, it's naturally not done and should be returned to backlog

Hi,

As you stated here:

 If the filter includes a global condition (not specific to a project), it means that you need to have 'Administer Projects' rights on all the projects in the JIRA instance. An example of such a filter is label = 'test' OR project = DEMO .

I have created a new board that uses a similar filter (i.e. project=AAA or labels in("test_label")) and even though I don't have administrative rights for all of the projects in JIRA I am able to create new sprints in this board (I am using JIRA 5.1.6 + GH 6.1.4.2). If using some other global condition, such as: project=AAA or custom_field=uuu, the "Create Sprint" button is greyed out, as mentioned in this article. So essentially the behaviour is as you described, except for when using labels. Am I missing something out? 

Thanks,

Petru

This behaviour may be affected by the field configuration of the custom field

Hi Rosie,

Thanks for your comment.

I was in fact talking about the labels feature in JIRA. Labels as far as I know are globally available though if you create a new board that uses labels in its filter it seems that you are able to create new sprints even if you don't have administrative rights on all the projects in the JIRA instance (as mentioned in this article). Don't get me wrong I think this is great  (otherwise we would have issues with using GH in our organization) but if this is the desired behaviour I think it should be documented in this article. Also, in my opinion you should have the right to create/start a sprint if you have administrative rights for the projects to which the issues from the backlog belong  - i.e the restrictions for creating/starting sprints should apply by taking into consideration the results returned by the board's filter and not the filter itself.

Kind regards,
Petru

I'd like to be able to set prelim start and end dates for all sprints on the planning board, not just when the sprint itself officially starts.  Then we might be able to see the estimated sprint window on the Team Calendar, and better plan our resources around the knowledge of leave dates, conflicting projects and so on.

Do I really have to set up separate temporary manual events in Team Calendar just to plan out dates for sprints?

Can I create a sprint with stories from multiple projects?

In our case we have multiple small projects, where the teams needs to work, hence a sprint needs to contain stories from separate projects. If this is not possible what's the workaround? Do we have to move these stories into a separate "working project"?