|Anonymous | Login | Signup for a new account||2019-04-19 07:29 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006940||TestLink||Bug Tracking Systems Integration||public||2015-02-11 15:53||2015-02-12 21:53|
|Priority||normal||Severity||feature request||Reproducibility||have not tried|
|Product Version||1.9.13 (2015 #1)|
|Fixed in Version|
|Summary||0006940: Allow disabling dynamic configuration in the config file|
|Description||The current JIRA REST dynamic configuration method is great but it brings some troubles for us . |
Currently it allows user to select "Issue Type", "Priority", "AffectVersions" and "Components", however,
1. Some of them are not mandatory fields for us so we don't need to select them during create issue.
2. Looks like we can not configure "Priority" via REST interface. It will always return an error. (Will paste the error message in the note once I got it again.)
3. We have some other mandatory fields that we have to configure during creating issue but we have no way to configure it in the dynamic configuration GUI. Looks like using static configuration is a way to solve it?
If we can have a config to disable/enable this feature in the config file, it would work for both users want to use dynamic configuration and users want to use static configuration.
|Tags||No tags attached.|
|QA Team - Task Workflow Status||TBD|
>> 2. Looks like we can not configure "Priority" via REST interface. It will always return >> an error. (Will paste the error message in the note once I got it again.)
no steps to reproduce, no error => this has no value
>> Currently it allows user to select "Issue Type", "Priority", "AffectVersions" and
my OUT OF THE BOX onDemand JIRA instance requests these attributes.
Surely because FIRST IMPLEMENTATION was released on 1.9.13 some minor adjustment like allowing BLANK value can be added.
This do not means that what has implemented is wrong.
Option on config file is not accepted because this create an system wide config, while we are trying to provide a config at issue tracking level.
Best solution (if will be implemented in future) will be a key on XML config at issue tracker level
Definitely this is a great feature, we are heading at the right direction.
>> Best solution (if will be implemented in future) will be a key on XML config at issue tracker level
Does this mean that we can specify the mandatory fields in the XML config so the dynamic configuration will get the Meta data from issue tracker for these fields and user can then select a value for any of these mandatory fields?
If user already specified a value in the XML config for these fields, then the default value for this field on the dynamic configuration GUI would be this specified value.
A solution that tries to leverage the static config (XML config) and dynamic config would be great.
Error message gotten when try to add issue with "priority" set:
addIssue:Failure:JIRA Message: priority => Field 'priority' cannot be set. It is not on the appropriate screen, or unknown.
However, I would assume this is a JIRA issue since I got similar error message when trying to use Python JIRA REST lib to create an issue with 'priority':
Field 'priority' cannot be set. It is not on the appropriate screen, or unknown.
By the way, we don't need to set "priority" during creating an issue. So it could be possible that JIRA admin may disable the permission for this.
is not a testlink issue, but as you have written a config problem on jira.
>>Does this mean that we can specify the mandatory fields in the XML config so the >>dynamic configuration will get the Meta data from issue tracker for these fields and >>user can then select a value for any of these mandatory fields?
No, because this is not the initial request on this ticket
What will be implemented at list on phase 1 is new key
<userinteraction> (Domain 1 or 0) </userinteraction>
1 => ignore attributes present on xml config, that can be retrieved asking the issue tracker. Currently this means affectedVersions,Components,Priority,issuetype
User will be able to choose values on GUI during issue creation
0 => no possibility for user to make choices on GUI, all values are those present on xml cfg.
some work will be needed to solve issues with custom fields
|2015-02-11 15:53||swang3||New Issue|
|2015-02-11 17:56||fman||Note Added: 0022679|
|2015-02-11 17:59||fman||QA Team - Task Workflow Status||=> TBD|
|2015-02-11 17:59||fman||Category||Bug Tracking System - JIRA Integration => Bug Tracking Systems Integration|
|2015-02-11 17:59||fman||Summary||Allow disabling the JIRA REST dynamic configuration in the config file => Allow disabling dynamic configuration in the config file|
|2015-02-11 18:01||fman||Description Updated||View Revisions|
|2015-02-11 18:02||fman||Note Added: 0022680|
|2015-02-11 18:12||fman||Note Added: 0022682|
|2015-02-12 02:30||swang3||Note Added: 0022686|
|2015-02-12 09:17||swang3||Note Added: 0022688|
|2015-02-12 21:47||fman||Note Added: 0022700|
|2015-02-12 21:53||fman||Note Added: 0022701|
|Copyright © 2000 - 2019 MantisBT Team|