Support forum for your suggestions, questions and to notify us of any issues you may encounter.
+3
Started

performance getting slow

Michael Terkowski 12 years ago updated by Matthew O'Riordan (Founder) 10 years ago 7
The performance of the app seems to deteriorate over time. When we first starting using easy-backlog in January, it was snappy and fast, and nowadays I'm getting lots of complaints from users in our teams that the tool is sluggy and slow, increasing resistance to using it.
Answer
Hi Roger, Michael and Torsten


We did a major deployment today, and we came across an error that was causing failed requests with Roger.  It turns out that his backlog was taking just under 6 seconds to render on the server, which is completely unacceptable.


Because of the urgency of this, we've devoted a fair amount of time today to finding a solution, and we've released some updates today that have brought that rendering time down to around 1.5s, so a 4x performance improvement.  Whilst this is good, this is not good enough, and we'll be working to improve that even further.


Obviously there is client-side rendering performance as well, and we'll be considering Torsten's suggestions here too, to ensure the performance remains snappy even when working with large backlogs.


Sorry for the problems, and hopefully we'll have it lightning fast again even for our heavier users.  I expect you'll notice the performance improvements already.


Thanks,

Matt

+3
Under review

assign story to sprint from different backlog

Roger Stich 12 years ago updated by sam 9 years ago 8
I had to plan Sprints with input from different customers (customizations of one big product) so i want to setup an enviroment where different people can edit there own backlogs (and only there own backlogs) and i can take the userstorys from there and build a sprint with storys from different backlogs.
Answer
Hi Roger

As it stands, you cannot build sprints from other backlogs.  Whilst I can certainly see a use case for this, this is quite niche functionality and would change the product quite significantly in that sprints will be divorced from backlogs.  This would effect everything.  What you can do however is let people work in their backlogs, and then move their stories to a central backlog when they are ready.  This can be done by using the move theme feature (tool icon next to a theme).  You could then allocate each user read access to the central backlog, and full access to their individual backlogs.

Do you think that would achieve the same result?
+3
Under review

I would like the ability to add tags to a story.

Bryan Oakley 12 years ago updated by Matthew O'Riordan (Founder) 12 years ago 2
We might have several stories spread across multiple themes that have to do with "reporting" or "training" or "editing". I would like to categorize my stories using such tags.
Answer
Hi Bryan

Thanks for the feedback.

Unfortunately I am really not clear what you are after.  Are you saying you want a story to belog to more than one theme?  And how are tags used?

Matt
+3
Under review

Points not up-to-date in sprint view (for asigned stories)

Bryan P 9 years ago updated by Matthew O'Riordan (Founder) 9 years ago 1
All to often user stories assigned to sprints show as zero points, even if points have been assigned in the backlog. The sprint summaries (total points) work, just not the story by story points.

Typically this problem seems to affect new user stories recently added since the sprint was crated and populated.
+3
Completed

allow to disable cost and daily rate

Michael Terkowski 12 years ago updated by Matthew O'Riordan (Founder) 9 years ago 2
not all scrum projects have daily costs and rates. we just want to use it for internal projects.
Answer
This feature was implemented, some time back!
+3
Under review

Themes should be tags

Barrett Cook 12 years ago updated by Matthew O'Riordan (Founder) 12 years ago 3
Themes affect the sorted priority of the backlog when planning for the next sprint.

It would be nice to group by tags, without affecting the ordering of PBI.

Regards,
Tagged
Answer
Hi Barrrett

I'm not sure I completely understand what you are asking for.  As you have said, currently stories are grouped under theme, so the theme ordering takes precedence over story ordering.  We are in fact considering an alternative view where you can order stories independently of themes, but we've not consolidated how this will work yet, so have not implemented this.  We are working on a solution though, so we will keep you posted on this.  You can see the discussion on this at http://easybacklog.userecho.com/topic/94379-drag-and-drop-ranking-of-backlog-independent-of-themes-eg-t1s1-t2s2-etc/

However, could you elaborate on what you mean by using tags so that I can understand that requirement?

Matt
+3
Under review

All stories list 0 points when assigning to sprint

Josh Fee 12 years ago updated by Matthew O'Riordan (Founder) 12 years ago 0
I just created my first sprint and after adding a few stories, the rest of them listed the points as 0. I went back to the backlog to verify that they had points listed, then back to the sprint where it was still listed as 0.

Refreshing the page fixed this.
Answer
Hi Josh

I've tried replicating this issue without luck.  Would you mind providing me with steps I can follow to recreate this issue, and could you also tell me what OS and browser you are using please?

Thanks,
Matt
+2
Under review

Allow public read access to backlogs without login.

Daniel Nüst 11 years ago updated by Matthew O'Riordan (Founder) 10 years ago 4

I develop an open source project and want to make the backlog available to all interested users of the software. For that a read-only version of the backlog that can be read without login would be great.

Answer

That's an interesting idea Daniel.  We've not had many people ask for this to date.  You could achieve this using our API, however this would of course require some development work on your end.  We'll consider the idea, however quite honestly unless more people ask for it it will be low on our priority list.

+2
Under review

Select stories to print

Louis van der Stam 11 years ago updated by Andrew Puddefoot 10 years ago 2
When printing stories to use in the planning phase, it would be nice to have the option to indicate which stories to print. The option to select stories to print based on the theme they belong to results in too many stories being printed. For us this was an issue when we updated a few stories in a theme and wanted to print only those.


Answer

Thanks for the suggestion.


Would it help if you could just print individual stories as that may be easier & quicker to implement, or do you think that would not really solve the problem as you need to print a few stories in a batch?  The problem with printing one at a time is it would be quite a waste of paper.


Thanks,
Matt

+2
Under review

Project Tasks section

Adam Shallcross 12 years ago updated by Rob Scott 10 years ago 4
It would be useful to have a section that allows you to add tasks that are kind of outside user stories.

So things like 
  • Setup development environment
  • Install Software
  • etc etc
It would be good to allocate time/cost to these also so they are not forgotten about when a client views the system as an overall cost for the project.

Cheers

Adam
Answer
Hey Adam

We are in fact thinking about allowing people to add tasks that are not following the strict "As a.." format, so these could be used for tasks outside of user stories.  Other than supporting a non "As a.." format, do you think you would need anything else, or would that suffice?

Matt