where is confleunec questions
Asked by Brane enterprises:

i am feeling disgusted..that for many things .....are not there when my development t teams are asking .every thing is linked to one app or so and it is linked to payments .

My team asked me they want confluence questions .when i checked its not there ....


Answers:
author: Nic Brough -Adaptavist-
body: I think you need to explain the problem a bit more. Questions for Confluence is fully available at [https://marketplace.atlassian.com/apps/1211644/questions-for-confluence?hosting=cloud\&tab=overview](https://marketplace.atlassian.com/apps/1211644/questions-for-confluence?hosting=cloud&tab=overview) so I'm stuck on what you mean by "not there"

comments: author: Trudy Claspill
body: I suspect that the poster is disappointed that Questions is not included by default as part of the core Confluence product, but must be purchased as an add-on app, based on the comment "linked to one app and it is linked to payments".


author: Brane enterprises
body: thats true . two days earlier when i checked for styles , the option is disabled and for this i have to buy scroll view report , for another option it asked me to buy bit bucket , now for this questions ..again another buy ...

this case for every small option/thing to develop , i cant buy many apps .....that will increase my project budget .

for mid to big companies like us , this is a bane ...

i am not satisfied with this way of buying apps for each and every option .

being a product owner ..dear team ...does this makes sense to you ?


author: Nic Brough -Adaptavist-
body: I see, you're asking about the "modular" nature of the Atlassian systems.

They work on the idea that you get a core system that does the basics for a particular group of tasks and extend it when you need it. So Confluence is a wiki, but if you want question functions you add it.

They do this because it's easier to maintain, administrate, and cheaper (especially for larger organisations), plus it usually gives your users a simpler interface with a less steep learning curve.

We regularly see people moving to Atlassian on the basis of complexity and cost. Systems that try to do everything can work very well, but they cost a lot for a load of functions you may not be using. Service Now for example is very good, does almost everything you could possibly want, but Jira Service desk does 75% of what everyone needs at a fraction the cost. And of the remaining 25%, adding the other 2% still keeps the costs way down.

But yes, the modular approach does feel very fragmented, and (assuming I've understood the US colloquialism, as I can't think of an English one) "nickel and diming the customer". There's not a lot anyone can do about that, it's the nature of "pick the bits you want".

I would recommend a review of requirements, earlier rather than later. To get you a bit of "Service Design". There's actually a lot of overlap in some of the pieces you may want - and if you're going to be looking at function A from app 1, you may find function 18 in app 3 also serves a similar or better way to do it. Obviously as a partner, I'm supposed to plug partner services for doing this (and of course, my own company does it all the time), but I would say it's not that hard - if you can put together the broad overview requirements and then find a friendly Atlassian geek (hint, there's a lot of us here), you can get a lot of advice to steer you through it.


Tags: cloud