Ok, thanks for the heads up, we'll get that sorted ASAP.

Thanks for your feedback.  It's a difficult one though, 11px was chosen to increase the quantity of text on the screen.  I appreciate 12px is more readable, but is that what everyone wants?  I am very reluctant to offer it as an option though as more options make the interface even more confusing.  Do you want to ask a few people to get their thoughts on font size so that we can get a consensus perhaps?

Sorry Will, but like Google Docs Spreadsheets (go and try it), this is actually not possible because the browser DOM does not report where in the HTML text you have clicked.  The alternative is to make all fields editable all the time, but then they would not wrap and would simply be single line / fixed height editable fields.  Unfortunately Will this one will not be solved any time soon.  It's on my to do list, but really not viable.

As this is not possible, this feature will not be included in future releases.

Thanks for the feedback mate, I will take a look and include in the next set of updates.

Nice idea, but unfortunately almost impossible because before you click on the text it's not actually an editable field, it's just plain HTML.  Once you have clicked, it's replaced with a text field which is why the cursor moves to the end (or the start on Mac).  I'll see what can be done, but I don't think this one will be easy to solve...

Sorry, I'm not clear on what you mean.  Each story ID is unique because it's prefixed by a Theme ID.

Can you not just put that in the acceptance criteria i.e. resolve ticket ID X?

I don't think we'll add this at this stage.  I understand the need for this, but it will certainly add a lot of complexity when we're actually trying to simplify things.  I'll keep this under review though and if other people feel this is needed, then we may well add this feature in future updates.

Yup, this is a minor bug.  However, once you have added the theme name you will see that the icons drop down to the correct positioning.  I will get this fixed in the next update.