v3.1.0: Batch update for Affected Version field doesn't work
1) I did the batch update with the affected version field, I selected 2-3 issues for the batch update.
2) After selecting a version in affected version field, click Update, it brought me back to the Issue view page of that component, but the affected version field has not changed.
3) I tried again with different field, Component field, the issues stayed in the same component as before.
4) Tried again with changing in Assigned To field, it did not take the change(s)
What is going on here?
kha
· 1 |
|
Thursday, September 10, 2009, 8:00:37 PM |
0
|
Are there any errors in the log? |
||||
|
0
|
There was no log showed at the time I tried to batch update. However, I can post the only log (below) that displayed in system log yesterday: I tried at about 2pm-3pm of 9/10/2009.
No Page.Request.UrlReferrer detected : /gemini/issue/ViewIssue.aspx9/10/2009 5:40:38 PM |
||||
|
0
|
We can not seem to replicate this. Can you try upgrading to 3.1.2 or better to 3.5.4.? |
||||
|
0
|
How much effort will it take to upgrade to v3.1.2? This is production server and there are lots of inside and outside clients are using this system. We don't want to make a big change when there is no plan or test for it first. So, definitely, we cannot upgrade to v3.5 for now. |
||||
|
0
|
Should not be difficult as it is a bug fix for 3.1. Replace web app and run create_procs and views. |
||||
|
0
|
I just exprienced more different things about this, narrow the problem down. |
||||
|
0
|
Is it possible for you to send a zipped backup of your database to support at countersoft dot com? |
||||
|
0
|
Unfortunately, the database contains sensitive information so we cannot send it out. |
||||
|