Actions
Feature #10153
closedThere is no specification set attribute
Start date:
03/06/2020
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
Even if the specification set value is different from 3.14 in the web-interface the attribute is always set to 3.14.
Updated by Ilja Zakharov over 4 years ago
- 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.
Updated by Evgeny Novikov over 4 years ago
- Is duplicate of Feature #6602: Report more attributes added
Updated by Evgeny Novikov over 4 years ago
- Status changed from New to Rejected
- Assignee deleted (
Ilja Zakharov)
There are many attributes to be reported actually - #6602.
Actions