We have been trialling the story map plugin over the last couple of months on a download installation of Jira and like it. I have a concerns about deploying to our production Jira instance in relation to performance.
I would like to know if you have any information on the performance of your story map plugin at scale?
We have a large Jira instance (Jira v5.1.6 with the Greenhopper plugin v6.0.5 and some other plugins. We are planning to upgrade to Jira 6.1 and the latest Greenhopper plugin in the next 6 weeks.)
I would like to know what type of footprint this plugin may add to my Jira instance:
If you have no performance data for the plugin - can you tell us what type of things (that may affect performance) we should test in the plugin (on a test instance of Jira) before we deploy this to production?
This add on adds no own custom fields or any additional data/indexes to your installation but uses only existing services. All the business logic is implemented at the client side – therefore no performance impact at the server side is expected! To show up the map once it needs one JQL- query – after that only little data is exchanged with the server.
Your questions in detail:
This add on can be used at your described configuration without hesitation and without any additional resources.
Let me know if there is anything else I can do for you!
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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