Hi Evgueni,
This evolution is not planned to come soon.
If you can find some funding, maybe you can use the new service : developement of evolution on request.
You will find details of this service on the "Service" menu.
As the evolution is estimated to 3 man*day, you will easily calculate cost, and you'll then determine if you concider it as reasonable.
Don't hesitate to contact me for more information.

Regards.
Babynus.

Hi All,

Requirements management is also a need I have in my use of Projectorria, for now I created a new type of ticket.

I am also interested to finance the development.

Babynus, can you describe your proposed implementation of this feature?

Best Regards

Hi,

Implementation planned to add item much like tickets.
With possibility to expand.
Any suggestion welcome.

Here is a possibility :

New screen "Requirement Type" :
- name
- code
- code
- workflow
- description : mandatory
- responsible : mandatory on handled status
- result : mandatory on done status
- lock handled : handled must be changed by status
- lock done : done must be changed by status
- lock closed : closed must be changed by status
- sort order
- closed

New sceen "Requirement" :
- Description
- id / reference
- project
- product
- product version
- type
- name
- external reference
- creation date/time
- description
- Treatment
- parent requirement
- status
- responsible
- handled
- done
- closed
- target version
- result
- Linked Elements
(link to any element : activity, document, ...)
- Attachments
- Notes

Regards.

Hi babynus

like i exchange with you in past, you can take a look at Jira implementation for this subject :

http://docs.optimizory.com/display/rmsis0130/Requirement+Attributes

from my point of view, you can add :
Estimated Effort : in man days
Priority: This field specifies priority of the requirement. Possible values for this field are "Blocker", "Critical", "Major", "Minor" and "Trivial".
Criticality: This field specifies criticality of the requirement. Possible values for this field are "Low", "Medium" and "High".
Feasibility:This field specifies technical and business feasibility of the requirement. Possible values for this field are "Yes", "No" and "Investigate".

Best Regards

Hi,

Thanks for this reminder.
I'll include it in the planned devs.

Some complements :
- estimated effort : can be in man days or hours, depending on selected unit.
- priority : list seems to refer to what is called "urgency" in Project'Or RIA
=> either name it urgency, and use existing urgency list (my preference)
=> or call it priority, but use existing priority list
=> or define new list : must then find a different name ...
- criticality : will use existing list
- feasibility : new list to build

Other points, from Jira requirements :
- requirement version : not planned.
=> interesting item, but may be complex to manage (not planned in a 3 day dev)
=> many fields should then be versionned
=> maybe other idea : set new requirement and define a field "replaces..."
- depends on (dependency management) : will be added
- baseline : not planned
- technical risk : can be added (new list)

Hi Babynus,

for requirements management we use Tickets with ticket type ="request". Especially since the new feature for "linked elements", we are happy with. Only thing we would need is requested start and end date, and estimated work and cost.

For our purpose it would be completely sufficient, to stay with Tickets. This reduces complexity.

Klaus