Does anyone actually find REAL answers here?

[Marcel Hager]

A little background information: I became a Jira/JSM admin about 4 months ago after a company acquisition and the preferred solution for ticket tracking of the acquiring company was JSM.

While attempting to learn the ins and outs of Jira/JSM I've spent A LOT of time on the Community forums looking for answers to questions I've had that the documentation doesn't explain well (or in some cases not at all).

The problem is that almost every single post that I find that is similar to my issue that are shown as "Solved" actually don't have a solution at all but basically comes down to "Jira can't do that" or "Try my company's app!"

Does ANYONE actually find real answers here to actual real problems or questions? I personally don't think that having to get a 3rd party app should count as "Solved", because it's really not.

[John Funk]

Hi Marcel - Of course people find real answers here!!  :-)

If you can point us to particular questions you have posted, we can take a look. Or if you create some specific problems for us.

[Trudy Claspill]

Hello @Marcel Hager 

"Solved" is perhaps a misnomer. What the authors are doing is accepting the answers provided. In some cases accepting an answer is an acknowledgement that there is no "solution" available from either native or vendor functionality. In other cases it is accepting that the only solution available is to leverage a third party product.

I personally have found many answers in this extended community, most recently in the area of the Assets functionality in Jira/JSM Data Center. Some of the answers were pointers to documentation that explained how to do what I wanted with native functionality. Some answers were suggestions about third party apps that could fill gaps where there was no native solution available.Some of the answers were confirmation that what I wanted to do couldn't currently be accomplished.

[Josh]

Hi @Marcel Hager .

The Community can be extremely helpful if you have proper expectations for what you'll get here. Here's my simplified view of things:

1. Tech Support / Specific Product Questions - Check your AI/search engine of choice and the Community first. If you don't find the answers you need, submit an Atlassian Support ticket. You'll most get some combination of answers, solutions, feature requests to vote on, and potential workarounds.
2. Non-Native Functionality - Check the Community for *ideas* but you will likely get pointed to marketplace apps or custom development consultants.
3. Business-Specific Requirements or Design Considerations - Check the Community for *ideas* but you may need to engage with a professional services firm if you need to talk through your specific use cases and specific recommendations provided to you.
4. Design Patterns / Ideas / Industry Trends - This is one of the areas where the Community has been most helpful for me. You often won't get a full solution, but you'll find out the platform constraints and what uses have tried to meet their needs. Then it's up to you to figure out how to apply those findings to your specific situation.