-
Bug
-
Resolution: Fixed
-
High
-
3.9.2
-
System Info
System Date Wednesday, 05 Sep 2007
System Time 11:32:49
Current Working Directory C:\WINDOWS\system32
Java Version 1.6.0
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.6.0-b105
Java Runtime Java(TM) SE Runtime Environment
Java VM Java HotSpot(TM) Server VM
User Name SYSTEM
User Timezone Australia/Perth
User Locale English (Australia)
System Encoding Cp1252
Operating System Windows 2003 5.2
OS Architecture x86
Application Server Container Apache Tomcat/5.5.20
Database type mssql
Database JNDI address java:comp/env/jdbc/JiraDS
Database URL jdbc:jtds:sqlserver://xxxxxxxxxxxxxxxxxxxxxxxxx
Database version 08.00.2039
Database driver jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2
External user management OFFJava VM Memory Statistics
Total Memory 278 MB
Free Memory 34 MB
Used Memory 244 MB
Memory Graph12 % Free (Force garbage collection)
JIRA Info
Uptime 6 days, 19 hours, 59 minutes
Edition Enterprise
Version 3.9.2
Build Number 235
Atlassian Partner
Installation Type EAR / WAR
Server ID xxxxxxxxxxxxxxxxxxDatabase Statistics
Issues 8487
Projects 10
Custom Fields 43
Workflows 15
Users 146
Groups 37File Paths
Location of entityengine.xml file:/D:/JIRA/atlassian-jira-enterprise-3.9.2-standalone/atlassian-jira/WEB-INF/classes/entityengine.xml
Location of atlassian-jira.log C:\WINDOWS\system32\atlassian-jira.log
Location of indexes D:\JIRA_DATA\Indexes
Listeners
Issue Cache Listener
com.atlassian.jira.event.listeners.cache.IssueCacheListener
Issue Index Listener
com.atlassian.jira.event.listeners.search.IssueIndexListener
Mail Listener
com.atlassian.jira.event.listeners.mail.MailListener
Transition Issues Awaiting Feedback On Comment (SFT)
com.atlassian.jira.toolkit.listener.AutoTransitionListener
Action ID: 731
Event ID: 6
Only do when current user is the Assignee?: false
Only do when current user is the Reporter?: false
Project Key: SFT
Status: 10000
Transition Issues Awaiting Feedback On Comment (SR)
com.atlassian.jira.toolkit.listener.AutoTransitionListener
Action ID: 751
Event ID: 6
Only do when current user is the Assignee?: false
Only do when current user is the Reporter?: false
Project Key: SR
Status: 10000Services
Escalate pending software SRs
com.atlassian.jira.jelly.service.JellyService
Delay: 6000000 minutes
input-file: d:\jira\jelly\escalate_overdue_software_srs.jelly
output-file: d:\jira\jelly\out.txt
Mail Queue Service
com.atlassian.jira.service.services.mail.MailQueueService
Delay: 1 minutes
POP service
com.atlassian.jira.service.services.pop.PopService
Delay: 1 minutes
usessl: No SSL
popserver: ferrari POP
handler.params: project=SR, issuetype=1, catchemail=xxxxxxxxxxxxxxxxxxxx
handler: Non Quoted Comment HandlerPlugins
Admin Menu Sections - 1.0
Plugin by Atlassian Software Systems
Enabled
Browse Project Operations Sections - 1.0
Plugin by Atlassian Software Systems
Enabled
Charting & Reporting - 1.3.9
Plugin by Atlassian Software Systems Pty Ltd
Enabled
Custom Field Types & Searchers - 1.0
Plugin by Atlassian Software Systems
Enabled
IMMT Customisations Plugin - 0.3
Plugin by Immersive Technologies Pty Ltd
Enabled
Improved HTML Plugin - 1.0
Plugin by SourceLabs
Enabled
Issue Operations Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
Issue Tab Panels Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
Issue Views Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
JIRA Toolkit Plugin - 0.7.22
Plugin by Atlassian Software Systems
Enabled
Portlets Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
Preset Filters Sections - 1.0
Plugin by Atlassian Software Systems
Enabled
Project Panels Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
Project Role Actors Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
RPC JIRA Plugin - 3.9
Plugin by Atlassian Software Systems Pty Ltd
Enabled
Renderer Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
Reports Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
SchedulePlanner Servlet - 1.0
Plugin by Rojo Networks, Inc.
Enabled
Scrum Backlog Report Plugin - 0.1
Plugin by Immersive Technologies Pty Ltd
Enabled
Show Saved Filter With Columns - 0.97
Plugin by Jes A
Enabled
Top Navigation Bar Sections - 1.0
Plugin by Atlassian Software Systems
Enabled
User Navigation Bar Sections - 1.0
Plugin by Atlassian Software Systems
Enabled
View Project Operations Sections - 1.0
Plugin by Atlassian Software Systems
Enabled
Web Resources Plugin - 1.0
Plugin by Atlassian Software Systems Pty Ltd
Enabled
Webwork Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
Wiki Renderer Macros Plugin - 1.0
Plugin by Atlassian Software Systems
Enabled
Workflow Plugin - 1.0
Plugin by Atlassian Software Systems
EnabledSystem Info System Date Wednesday, 05 Sep 2007 System Time 11:32:49 Current Working Directory C:\WINDOWS\system32 Java Version 1.6.0 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.6.0-b105 Java Runtime Java(TM) SE Runtime Environment Java VM Java HotSpot(TM) Server VM User Name SYSTEM User Timezone Australia/Perth User Locale English (Australia) System Encoding Cp1252 Operating System Windows 2003 5.2 OS Architecture x86 Application Server Container Apache Tomcat/5.5.20 Database type mssql Database JNDI address java:comp/env/jdbc/JiraDS Database URL jdbc:jtds:sqlserver://xxxxxxxxxxxxxxxxxxxxxxxxx Database version 08.00.2039 Database driver jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2 External user management OFF Java VM Memory Statistics Total Memory 278 MB Free Memory 34 MB Used Memory 244 MB Memory Graph 12 % Free (Force garbage collection) JIRA Info Uptime 6 days, 19 hours, 59 minutes Edition Enterprise Version 3.9.2 Build Number 235 Atlassian Partner Installation Type EAR / WAR Server ID xxxxxxxxxxxxxxxxxx Database Statistics Issues 8487 Projects 10 Custom Fields 43 Workflows 15 Users 146 Groups 37 File Paths Location of entityengine.xml file:/D:/JIRA/atlassian-jira-enterprise-3.9.2-standalone/atlassian-jira/WEB-INF/classes/entityengine.xml Location of atlassian-jira.log C:\WINDOWS\system32\atlassian-jira.log Location of indexes D:\JIRA_DATA\Indexes Listeners Issue Cache Listener com.atlassian.jira.event.listeners.cache.IssueCacheListener Issue Index Listener com.atlassian.jira.event.listeners.search.IssueIndexListener Mail Listener com.atlassian.jira.event.listeners.mail.MailListener Transition Issues Awaiting Feedback On Comment (SFT) com.atlassian.jira.toolkit.listener.AutoTransitionListener Action ID: 731 Event ID: 6 Only do when current user is the Assignee?: false Only do when current user is the Reporter?: false Project Key: SFT Status: 10000 Transition Issues Awaiting Feedback On Comment (SR) com.atlassian.jira.toolkit.listener.AutoTransitionListener Action ID: 751 Event ID: 6 Only do when current user is the Assignee?: false Only do when current user is the Reporter?: false Project Key: SR Status: 10000 Services Escalate pending software SRs com.atlassian.jira.jelly.service.JellyService Delay: 6000000 minutes input-file: d:\jira\jelly\escalate_overdue_software_srs.jelly output-file: d:\jira\jelly\out.txt Mail Queue Service com.atlassian.jira.service.services.mail.MailQueueService Delay: 1 minutes POP service com.atlassian.jira.service.services.pop.PopService Delay: 1 minutes usessl: No SSL popserver: ferrari POP handler.params: project=SR, issuetype=1, catchemail=xxxxxxxxxxxxxxxxxxxx handler: Non Quoted Comment Handler Plugins Admin Menu Sections - 1.0 Plugin by Atlassian Software Systems Enabled Browse Project Operations Sections - 1.0 Plugin by Atlassian Software Systems Enabled Charting & Reporting - 1.3.9 Plugin by Atlassian Software Systems Pty Ltd Enabled Custom Field Types & Searchers - 1.0 Plugin by Atlassian Software Systems Enabled IMMT Customisations Plugin - 0.3 Plugin by Immersive Technologies Pty Ltd Enabled Improved HTML Plugin - 1.0 Plugin by SourceLabs Enabled Issue Operations Plugin - 1.0 Plugin by Atlassian Software Systems Enabled Issue Tab Panels Plugin - 1.0 Plugin by Atlassian Software Systems Enabled Issue Views Plugin - 1.0 Plugin by Atlassian Software Systems Enabled JIRA Toolkit Plugin - 0.7.22 Plugin by Atlassian Software Systems Enabled Portlets Plugin - 1.0 Plugin by Atlassian Software Systems Enabled Preset Filters Sections - 1.0 Plugin by Atlassian Software Systems Enabled Project Panels Plugin - 1.0 Plugin by Atlassian Software Systems Enabled Project Role Actors Plugin - 1.0 Plugin by Atlassian Software Systems Enabled RPC JIRA Plugin - 3.9 Plugin by Atlassian Software Systems Pty Ltd Enabled Renderer Plugin - 1.0 Plugin by Atlassian Software Systems Enabled Reports Plugin - 1.0 Plugin by Atlassian Software Systems Enabled SchedulePlanner Servlet - 1.0 Plugin by Rojo Networks, Inc. Enabled Scrum Backlog Report Plugin - 0.1 Plugin by Immersive Technologies Pty Ltd Enabled Show Saved Filter With Columns - 0.97 Plugin by Jes A Enabled Top Navigation Bar Sections - 1.0 Plugin by Atlassian Software Systems Enabled User Navigation Bar Sections - 1.0 Plugin by Atlassian Software Systems Enabled View Project Operations Sections - 1.0 Plugin by Atlassian Software Systems Enabled Web Resources Plugin - 1.0 Plugin by Atlassian Software Systems Pty Ltd Enabled Webwork Plugin - 1.0 Plugin by Atlassian Software Systems Enabled Wiki Renderer Macros Plugin - 1.0 Plugin by Atlassian Software Systems Enabled Workflow Plugin - 1.0 Plugin by Atlassian Software Systems Enabled
-
3.09
-
In one of our projects (SFT) we've just implemented a security scheme. Now, when we move issues from that project to another (VDB) without a security scheme they can no longer be viewed or edited by anyone. Instead an error message stating "Permission Denied" occurs.
I've verified this is occurring by looking at the database directly. Looking at the record in the "jiraissue" table for one of the problem issues (VDB-491) I've observed that the "security" field remains set after the move - even though the security scheme referenced is not applicable for the new project, VDB. Now, if I directly make the field null for the issue in the database , as it would be if the issue was created directly for that project, the issue magically appears.
Obviously issues effectively disappearing is very bad. The only workaround that I can think of is to apply the security scheme to ALL projects as issues may be moved between various projects.
In terms of implementation it seems like there would be two ways to solve this. Once would be to clear the security field as part of the move. The other would be to ignore the security field if the project that the issue is associated with has no security scheme. The second approach appears more favorable as it means that if you move the issue back to the original project then the (probably) appropriate security level is maintained.
I'm also convinced that the above is happening due to something I noticed when I initially applied the security scheme. I accidentally canceled the operation and was left with half the issues in the project inaccessible. From what I could tell this was because the security field had been set for those issues but the security scheme had not been set for the project. Presumably this done after all the issues have been updated? In that case the fix was just to run through the operation again but it's a bit of a trap so might also want to be addressed.
Regards,
Simon
- details
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
