This is something general and not technical. As we know that the strength of JIRA from user community is the feasibility to do extensive customization. How will the users prefer the JIRA cloud instance when they are not ready to support non-Atlassian plugins?
Now this document seems that they are removing the currently supported ones as well. Is my understanding wrong? Is Atlassian planning to provide solutions via some other means like their own features?
You are correct.
First, as a managed service, Atlassian can only afford to support a limited range of functions. They've chosen the add-ons they are willing to support carefully, and locked out the rest (especially ones that might allow users to create "interesting" breaks in the system).
Note that you can still install add-ons. Connect add-ons talk to the Cloud systems via interfaces that Atlassian can, and do support. Atlassian are trying to remove the reliance on non-Connect add-ons and move as many functions into Connect add-ons as possible (or into JIRA Core)
If a user needs something that can't be done on Cloud, then they have to use Server.
There are alternatives to Atlassian cloud - other cloud offerings based on AWS, Google cloud or Rackspace or others which combine the benefits of both worlds - service like solution for the end user and all the Server add-ons.
Number of Atlassian experts provide such services or you can set it up yourself.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs