[JohnO]

Hello Nicolas,

another question about “rank”.

When I sort my backlog in iceScrum by rank (default sort criteria in list view), then iceScrum will sort the backlog items in “Ascending” order. I assume that this means that the item at the top has the lowest rank and the item at the bottom has the highest rank.
Is my assumption correct?

If it is, then this is the opposite of the behaviour that I would expect i.e.

As a Product Owner
I want that my most important backlog items appear at the top of the backlog
So that I can quickly identify the items I want to implement next
😉

At the moment, in order to display my most important backlog item at the top of the list, I have to change the sort order to “Descending”. Correct?

Regards,
John

[JohnO]

Hi Nicolas,

thank you for the quick response.

Yes, that make sense. I had not known that I could drag & drop items to reorder the backlog. I tried it just now and it works. So dragging an item to a new position in the backlog (up or down) will change the “rank” of that item and when I sort by rank I can restore the backlog to that order. Nice feature!

Now I understand it completely.

Thank you!
John

[JohnO]

OK, it seems like the “Advanced Search” feature that I read, was desribed in the old (R6) documentation. Problem solved.

[JohnO]

OK, I have found out how to define actors and how to reference an actor when writing a story using the “@” symbol.
However, I still cannot find the “Advance Search”.

[JohnO]

Hi,

I read in the documentation that is possible to definine Actors. Nice feature.
Is there a way of somehow selecting the actor for a particular story?

As a scrum master
I would like to restrict the actors used in the Story description to a certain set of actors
so that I can avoid other colleagues from “inventing” a new actor with every story they write.

I also read that searching for stories using these actors. However, I cannot find out how to perform an advanced search, e.g. searching for all stories for a particular actor.

Here is an except from the documentation:

“…Usage

IceScrum search bar is available on the top right corner of the grey toolbar. You can use it to find elements in each of these views : Sandbox, Product Backlog, Sprint plan and Icebox . To do an advanced research, you have to click on the last button of the iceScrum blue toolbar. In the drop-down list choose “Finder”.

Advanced Search

You can search for any iceScrum elements (tasks, stories, features, actors) in the unified finder view, they will then appear classified by sort of element. Various filters are available to help you find exactly what you are looking for….”

Where is the “Blue Toolbar”? I have searched and searched but can’t see any blue toolbar. A screen shot would be nice.

[JohnO]

Dear Nicolas,

We use teams in the cloud.

Regards,
John

[JohnO]

Dear Nicola,

thanks. I agree “concise, simple and homogeneous”, but why does that rule out the use of formatting?
Just as in the acceptance tests, the use of Gherkin language is emphasised by bold lettering, I would like to emphasise the use of the user story keywords i.e.

“As ”
“I want ”
“so that ”

using bold type. This helps to focus the writer’s/reader’s attention on the correct format of a user story.
Just an idea, maybe you can consider it for a future version?

• This reply was modified 4 years, 4 months ago by JohnO.

[JohnO]

Dear Nicolas,

thank you for the swift reply!

Unfortunately, German is not offered when selecting a language in my profile. However, this was not my issue. I wanted to know how to set up a template for my stories with German content and reuse this template when creating new stories.
I found out how to do this using the template “app” – although it is not really a template, more like an instance of a sample story. So far so good!
Now another question: when defining the acceptance tests, via the “Tests” tab, the text-editor offers me the possibility of formatting the text so that I can render certain words in Bold, Italic etc. I like this feature!
However, when I write the description the story via the “Details” tab, it is just plain text. How do I enable the tools for formatting the description of the story similar to the acceptance tests. I could not find anything in the documentation about this.

Best Regards,
John

[Author]

Posts