Field Visibility - same for all issue type
We need to hide some issue fields for our customers. So we created Field Visibility Scheme, assigned it to project and noticed that it doesn't work... We also tried to assign this scheme to all issue types and now it works. But there is some strange behaviour while editing issue: when issue type is changed then page is reloaded. It require some time to reload page (distract user) and some values are lost! For example: Status or custom fields.
We just need to hide some issue fields for project (it not depends on issue type or if user is creating or editing issue).
Please let me know how to set up Gemini to get it work.
Thank you
We use Gemini 3.5.3
stepand76
· 504 |
|
Thursday, August 27, 2009, 10:09:58 PM |
0
|
Field Visibility Schemes are applicable to individual Issue Type(s). You will need to apply the same FVS to Create and Edit mode for all Issue Types. Some Fields might not be visible after the Issue Type is changed on Issue Create or Edit screen depending upon the Field Visibility Scheme that is set for the Issue Type. |
||||
|
0
|
I understand, but why page is reloaded when changing issue type if all issue types have the same FVS? |
||||
|
0
|
3.6 will address this issue. |
||||
|
0
|
Thank you! When we can expect 3.6? |
||||
|
0
|
We are hoping to have 3.6 out by the end of this month. |
||||
|
0
|
[quote user="MarkWing"]We are hoping to have 3.6 out by the end of this month.[/quote] |
||||
|
0
|
Yes, BETA should be out this week. |
||||
|
0
|
[quote user="SaarCohen"]3.6 will address this issue.[/quote] |
||||
|
0
|
Can you please explain further? What is going wrong? |
||||
|
0
|
See my first post. The anoyance is that values in some fields are lost when changing issue type (creating or editing an issue). |
||||
|
0
|
We will have another look at this. I think I understand the issue now, the default values re-apply correct? |
||||
|
0
|
[quote user="MarkWing"]We will have another look at this. I think I understand the issue now, the default values re-apply correct? |
||||
|
0
|
|
||||
|
0
|
Thanks, but it's a pitty it is for 3.7. How long we will wait for 3.7? |
||||
|
0
|
3.7 is around 3 months away. The workaround is to select the issue type first. |
||||
|
0
|
OK, thanks for the info. I hope you fix it for 3.7 and release it during the spring. This issue was important to our decision to buy a subscription half a year ago... |
||||
|
0
|
:( |
||||
|
0
|
Sorry to disappoint you. I was told that it will be done for 4.0, which is due out by the end of the summer. |
||||
|
0
|
But it will require renew license subscription. |
||||
|
0
|
That depends on when your license expires. |
||||
|
0
|
8/5/2010 |
||||
|
0
|
Well, hopefully 4.0 will be out by August in which case you will not need to renew. |
||||
|