In a meeting of the EA user group a few years ago in Netherlands, I did a talk about ‘which bits of EA do people really use?’.
And, based on a non-scientific, but probably representative sample of 150 EA users from all over Europe, almost nobody used the Element resource, element issues ideas: people who do Project Management seemed to use MS Project, or similar tools. And those who do issue tracking overwhelmingly use Jira (see recent announcements from Sparx and Proaborate)
They din’t use EA.
For that time on, we changed our development approach to concentrate on core EA function, and stopped trying to support do all the strange stuff which Sparx build into EA.
I understand this is no help to you, but we have a finite amount of development time, and we want to help the majority of our users.
So for this reason, we have not, and don’t propose to, make Element Issues, -Resources, -Risks, or -Effort a priority for either eaDocX or eaXL development. So there will be nothing new on those areas in eaDocX V4.
I’m saying this because we are 100% driven by what our users tell us they need from eaDocX and eaXL, and this sadly means that everyone can’t have everything they need.
Even if they really need it.
Thanks for your understanding.
Ian M
