![]() It's a "return on investment" that can work, reducing your income to make something a bit more widely used, but finding out where it might work in the Atlassian ecosystem is probably a mathematician's Master's thesis. Think of it this way - you would be adding costs to allow people to reduce your income. The last 1% I'd add is that a lot of app writers see the costs of writing and maintaining code to handle that sort of thing as high. Rosenlund _Seibert Media_ and Benson _draw_io_ have covered 99% of what I would like to say on the subject far more clearly than I could. I'm not going to ramble about the pricing considerations that vendors make myself. Having plugins query them further constantly is going to make it even slower, and quite simply put, it does not scale. Checking them at project level is already pretty slow. Then there's a deeper one - permissions in Atlassian applications are a bottleneck.You can probably imagine that most plugin authors went "nope". They went with "if your plugin wants to do this, you'll have to code for it yourself". Atlassian kept it simple and simply didn't bother investing huge amounts of time in providing a framework that could cope with all cases. You can probably see how complicated all of those might be to code for.And then there's the ones that added workflow functions - should a workflow stop working (or even behave differently) because you've used a plugin workflow function that isn't valid in the project you've just associated it with because the wrong people are members of the project? Or you've added someone who doesn't have a licence?.Do you really want admins to have to deal with regular reports of "my reports stopped working after I added a new person to the project"? Or a report, which you might control by project. ![]() Sure you could say things like "only people in group X can add gadget Y to a dashboard", but then what do you do with someone viewing it? Should they need a licence?.Next, the plugin framework couldn't do this by project or user or anything else for all types of plugin. This immediately made your job as an admin more complicated because you had to match up who might use something against where it might be used and how and then somehow maintain that. Many years ago, we could actually have apps (then "plugins") which you could licence for sub-sets of your users. The main reason they've done this is simplicity. 297 13,296 installs CLOUD FORTIFIED Supported Jira Service Management Jira Software Try it free Cloud Overview Reviews Pricing Privacy & Security new Support Versions Installation The most advanced Jira portfolio management tool. The simple answer is "because that's the model Atlassian have chosen".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |