Query resolutions with Jira inbuilt functions

[Mayuresh Athalekar]

Whenever i try to search some query for resolution on Jira community, i see that more or less all answers are coming from Marketplace partners who have developed some plugins and promote their plugins. I agree that this is a good marketing strategy to promote ones plugins, it is not a viable option to adopt for most companies who work in secured environment or centrally managed Jira infrastructure / environment.

In my case, i WONT be able to make use of any plugins since my company policy doesn't allow external plugins.

I am afraid, i am not seeing any answers from Atlassian development members to provide solutions with inbuilt functions and that is a very bad experience, IMO for users who are heavily relying to inbuilt functions.

Please guide, how we can proceed further to resolve queries !

[Sachin Dhamale]

@mayuresh athalekar ,

I am not agree with you. First priority will be always in built functionality. If In built functionality can resolve the issue then definitely i would suggest that first.  If not then I suggest the workaround using in built functionality it self.

Third option would be the plugin/script development. Atlassian has API through which you can built any kind of plugin by your self provided you should have the knowledge and time for the same. if not then at last we suggest the third party plugin.

At the end of the day its your choice to go with the plugin or not. 

I don't think anyone is using this platform to promote the third party plugin. Main intention will be to resolve the issue in any ways. 

I can see that some of the time we get the third party plugin as a solution but it does not mean that they are promoting the plugin.

[Nic Brough -Adaptavist-]

That's a very interesting question.

I work for a partner, one with products, but I personally try not to answer with "you'll need <adaptavist product>".  I find the knee-jerk marketing responses from some other partners quite grating when it's "use our app" instead of "here's how you can do it natively" or even "this is why you can't do it (but our app does)".

If you can do it without an app, then you should, but "you'll need an app like <xyz>" is a good answer in places, as is "well you could, but this app makes it a lot easier"

I'm commenting here to make sure I get notified about the conversation.  I don't have an answer or much to contribute, especially because I work for one of the partners who provide apps, so I know I'll be seen as biased (the more SR/other apps I can sell, the better my wallet looks!), but this is a very interesting topic for me.