Entered stories don't show up in agile board in OnDemand environment

Dear atlassians,

I am using JIRA + Greenhopper since several years, where the software was installed in a customer environment. Now I've started using JIRA+greenhopper with on demand service (just signed up on Monday) and this works not as expected.

Here my steps to reproduce:

I just created a new agile project as administrator which I called sbox (SBOX). The project shows up in the planning board.

Then I add a few new stories (also using my administrator account).

Problem: The stories don't show up in the backlog. No filter is active, such as "only my issues" or "recently updated".

But I don't see these. I can only see the new stories wihtin the regular JIRA issues list. I didn't do any change in the basic configuration, meaning adapting the workflow or so. I even didn't create any user account yet.

I tried to create another agile project with the same result.

I've tried to import the sample project (SSP) and this seems to work as expected showing entries within the backlog.

In my eyes, this seems to be a JIRA/Greenhopper problem. I need urgent help, since we want to start our first sprint these days.

2 answers

The following information was helpful to guide me into the solution:

https://confluence.atlassian.com/display/GHKB/Your+issue+XXX+has+been+created+but+is+not+currently+visible+on+the+Rapid+Board

The problem is, that a new project doesn't get the Greenhopper workflow scheme assigned.

Check if the issues are part of the boards filter and make sure the status they are in when you create the is mapped to a column of your board

The problem within the project has been fixed by manually applying the greenhopper workflow and then by following the steps to properly map the workflow steps by hand. Additionally, I had to apply the workaround for GHS-5741 as described in https://confluence.atlassian.com/x/hAX7EQ

All in all, it works now, but it is hard that you run into such problems, because the only thing I wanted is to get it working as with the SSP project and this doesn't come out of the box with the currently provided new project assistent as described in my initial report (see top of page). I can see, that other people might also run into the problems, because I was just using the assistent which was bringing the new project into an inconsistent state.

So I'm still interested, if there are any actions taken by the greenhopper/jira on-demand team to fix this.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

247 views 0 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot