We have moved to a new Sailfish OS Forum. Please start new discussions there.

break down your ideas/feature requests

asked 2013-12-24 20:01:26 +0300

Low gravatar image

updated 2014-12-07 02:51:18 +0300

simo gravatar image

I think it'd be very nice for the overall traceability here if all of us could break down ideas and feature requests into single features / behaviors. I see many posts here that go "ideas for xyz application" and then list like 3 or 4 single features. While this is nice to write from the top of your head, we'll wind up with a shipload of overlapping posts.

edit retag flag offensive close delete



...I also did this I have to admit:)

Low ( 2013-12-24 20:06:54 +0300 )edit

5 Answers

Sort by » oldest newest most voted

answered 2013-12-24 20:49:54 +0300

lbt gravatar image

I've been trying something out too. Let me explain my reasoning first.

There's an Unanswered section.

I think this is a place where Jolla users (as well as sailors) can answer general questions which are achievable without Jolla having to develop a feature or code. Development help; support with general usage - that kind of thing.

I think the "Jolla, can you add feature XYZ?" questions clog this up - but they're still valuable and we still want them asked (and answered!).

Basically I want to keep the Unanswered area useful for our community because it's easy to access and a great way to help each other out.

So I'm adding some boilerplate answers to these feature request questions and adding a tag voteforme

What this means:

  • The Unanswered section should have questions that the community can answer - go, answer them!
  • Please add voteforme to questions which you want others to support
  • Click on a voteforme tag and vote for things you want Jolla to do - we're listening (and this will allow us to show the top voted items)

If this doesn't work out then please add feedback here and I'll revert it :)

Nb one idea I have is to ask @eric to make the Unanaswered section skip questions marked voteforme

edit flag offensive delete publish link more


Anyone posting an idea wants it to be supported... don't they?

chemist ( 2013-12-24 20:52:26 +0300 )edit

nb - anyone with enough karma can help out here and also do the retagging; I suggest people only add the boilerplate after retagging with voteforme otherwise we risk losing track of questions.

lbt ( 2013-12-24 20:52:49 +0300 )edit

@chemist - yes, exactly - ideas want support but questions want answers! I bet we could have an 'Ideas' section next to unanswered too

lbt ( 2013-12-24 20:53:23 +0300 )edit

[idea] or [feature-request] would be the proper tag for things like that. I don't want votes, I like to believe that I'm not narcistic - so I rather put a [meta] tag because that's what this idea or question is about. Also, questions->ideas here don't have to be answered as in answering a question. An answer can also be a reaction by Jolla on ETA or so.

Low ( 2013-12-24 21:06:21 +0300 )edit

@Low - I can accept that you're not narcissistic :) The idea was to positively encourage feedback. We actually a) want people to vote and to b) realise that voting is listened to. The tags are just metadata in a DB. We can do a mass substitution if I chose the wrong tagname.

lbt ( 2013-12-24 21:14:31 +0300 )edit

answered 2013-12-24 20:52:28 +0300

Low gravatar image

right, this doesn't require an answer.

edit flag offensive delete publish link more



I think it does... Some ideas breaks into details, some affect too many other details. Bugs are easy, but questions around UI or a larger app are hard to handle the way you suggest. We'll either have too large answers with multiple details, or too many questions+answers around the same subject.

simo ( 2013-12-26 07:27:04 +0300 )edit

if we're talking about a concept of usability or workflow, yes there will be longer posts and a lot of discussion to refine it. And it will be good.

I'm more talking about those large apps with a lot of aspects to improve. If everyone is just making a post with their 10 different improvements to that large app, where only one or two are essentially different from other hands' posts, this is headed for the seas of chaos. Even worse, maybe there's a really bright feature but it gets sunk to the bottom because it comes with 4 overlapping aspects and another 4 that are plain unacceptable.

A similar line of thought are btw those "can I have xyz browser/email/im exactly like on my iphone/android/PC/car?"...if you wanted to have everything exactly like on your droid, why didn't you buy one? this is a bit meta, but before asking such a question, rather ask yourself: what is the feature I miss compared to the existing application - is it syncuing to your other devices, is it the workflow?

Low ( 2013-12-26 10:50:42 +0300 )edit

answered 2013-12-25 13:29:23 +0300

lbt gravatar image

Following up in another (votable) answer: To make it more seamless how about an Ideas section right up there between Unanswered and Followed which would show these wish-list question (ie similat to clicking on a voteforme tag) and the Unanswered section would exclude them.

edit flag offensive delete publish link more

answered 2013-12-26 02:13:10 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2013-12-26 02:17:56 +0300

Nux gravatar image

I think you can just use tags for that (like some people seem to already be using) and then click on the tag and use sorting and further filtering.

From what I seen:

  • Use "bug" tag - for bugs.
  • Use "feature-request" - for system/Jolla feature requests.
  • Use "idea" - for request that cannot be fulfilled by a change in single application/module.
  • use "support-request" - for things that need support (or move to jolla.zendesk.com as it seem to be working and is more private).

Edit: Adding as a "wiki" answer, not sure where it should land.

edit flag offensive delete publish link more

answered 2015-09-13 16:21:12 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2015-09-13 16:21:12 +0300

simo gravatar image

The Guideline project:

I just checked this guideline to start from the oldest. I'm considering picking up some important issues mentioned here, and adding those to guide topic "Posting ideas and feature requests" (under "Posting new questions"). What might be valuable and up to date, worth picking up from this thread:


  • Idea posts are allowed to include lots of new features in the same post
  • They are more discussive by nature
  • They might not necessarily reach an accepted answer at any point, but ideas gathering lots of votes could be broke down to feature requests listed on the original idea post
  • The post should be tagged at least with idea

Feature requests

  • Feature request post should present only one new feature / question
  • They can be answered with ideas how to implement the feature
  • Accepted answer is the selected implementation (if reaching the roadmap)
  • The post should be tagged with feature-request and with few tags where the request might affect, like certain app, certain screen, certain gesture etc.

The guideline project discusses on these old guideline posts until September 20th, updating and gathering information from here to a new post The Guideline. You're welcome to join the project, for example by editing and commenting this answer.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

1 follower


Asked: 2013-12-24 20:01:26 +0300

Seen: 1,239 times

Last updated: Sep 13 '15