I believe that we ought to focus our backlog refining on user stories that are not set with low priority
the essence of this user story is as relevant as it was. We will have 90+% of the functionality of a cause-effect tool in our problem grouping solution in Flyt. A digital tool for quick and easy cause-effect analysis is very interesting to have.
but the wording is wrong since we no longer use the image of a fish in Flyt. I am prepared to update user story after I have more actual experience with using the coming feature of grouping problems (dependency)
User story As an end-user I want to be able to use the Fishbone stand alone, but then with Sticker in “mouth of fish” for brain storming sessions