Feature #10153
closed
There is no specification set attribute
Added by Ilja Zakharov over 4 years ago.
Updated over 4 years ago.
Category:
Infrastructure of Core
Description
Even if the specification set value is different from 3.14 in the web-interface the attribute is always set to 3.14.
Related issues
1 (1 open — 0 closed)
- Tracker changed from Bug to Feature
- Subject changed from The specification set attribute has an incorrect value to There is no specification set attribute
- Priority changed from Immediate to Urgent
- Detected in build deleted (
svn)
It seems that there is no any attribute that specifies specifications set version. There are attributes for a fragmentation set version and tactic, for example. So to distinguish different specification sets we need a new attribute.
- Status changed from New to Rejected
- Assignee deleted (
Ilja Zakharov)
There are many attributes to be reported actually - #6602.
Also available in: Atom
PDF