[JIRA] (JENKINS-15351) Exception while processing cpd report.
Ulli Hafner updated JENKINS-15351 Exception while processing cpd report. Change By: Ulli Hafner (29/Sep/12 7:08 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15357) Adding test articacts as attachment to Testopia testcases
Peter Florijn created JENKINS-15357 Adding test articacts as attachment to Testopia testcases Issue Type: Improvement Affects Versions: current Assignee: Bruno P. Kinoshita Components: testopia Created: 29/Sep/12 7:38 AM Project: Jenkins Priority: Major Reporter: Peter Florijn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15357) Adding test artifacts as attachment to Testopia testcases
Peter Florijn updated JENKINS-15357 Adding test artifacts as attachment to Testopia testcases Change By: Peter Florijn (29/Sep/12 7:39 AM) Summary: Adding test articacts artifacts as attachment to Testopia testcases This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15358) Plotting of CSV does not qwork correctly, data out of sync with graph
Peter Florijn created JENKINS-15358 Plotting of CSV does not qwork correctly, data out of sync with graph Issue Type: Bug Affects Versions: current Assignee: nidaley Attachments: plot plugin error.png Components: plot Created: 29/Sep/12 10:01 AM Description: I created a csv file with mysqlslap benchmark to0l and wanted to plot the AVG, MIN, MAX values. I experimented with the settings of the plugin and I am experiencing some problems to get the correct graph. It seems like there is some syncing problem between the data used for the graph and graph showed (see attachment) Environment: OSX Mountain Lion, Firefox browser Project: Jenkins Priority: Critical Reporter: Peter Florijn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15358) Plotting of CSV does not work correctly, data out of sync with graph
Peter Florijn updated JENKINS-15358 Plotting of CSV does not work correctly, data out of sync with graph Change By: Peter Florijn (29/Sep/12 10:05 AM) Summary: Plotting of CSV does not qwork work correctly, data out of sync with graph Description: I created a csv file with mysqlslap benchmark to0l tool and wanted to plot the AVG, MIN, MAX values. I experimented with the settings of the plugin and I am experiencing some problems to get the correct graph. It seems like there is some syncing problem between the data used for the graph and graph showed (see attachment) The csv file is produced in a shell command build like this:echo "LABEL1, LOAD_TYPE, AVG , MIN , MAX, NR_CLIENTS, AVG_NRC_QUERY" > header.txtmysqlslap -uroot -a --csv=results.csv --concurrency=100 --number-of-queries=1cat header.txt results.csv > report.csv This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15359) Adding a second data series and saving it results in error
Peter Florijn
created JENKINS-15359
Adding a second data series and saving it results in error
Issue Type:
Bug
Assignee:
nidaley
Components:
plot
Created:
29/Sep/12 10:10 AM
Description:
Failed to parse form data. Please report this problem as a bug
JSON={"":"","builder":{"command":"echo \"LABEL1, LOAD_TYPE, AVG , MIN , MAX, NR_CLIENTS, AVG_NRC_QUERY\" > header.txt\nmysqlslap -uroot -a --csv=results.csv --concurrency=100 --number-of-queries=1\ncat header.txt results.csv > report.csv","kind":"hudson.tasks.Shell","stapler-class":"hudson.tasks.Shell"},"core:apply":"","description":"","displayNameOrNull":"","name":"Mysqlslap","properties":{"com-coravy-hudson-plugins-github-GithubProjectProperty":{"projectUrl":""},"hudson-model-ParametersDefinitionProperty":{},"hudson-plugins-sidebar_link-ProjectLinks":{},"org-jenkinsci-plugins-envinject-EnvInjectJobProperty":{},"stapler-class-bag":"true"},"publisher":[{"kind":"hudson.plugins.plot.PlotPublisher","plots":{"csvFileName":"167550448.csv","group":"MySQLslap","numBuilds":"5","series":[{"file":"report.csv"},{"file":"report.csv","fileType":{"displayTableFlag":false,"exclusionValues":"","inclusionFlag":"OFF","url":"","value":"csv"}}],"style":"line","title":"MySQL performance","useDescr":true,"yaxis":""},"stapler-class":"hudson.plugins.plot.PlotPublisher"},{"docs":{"description":"","directory":"","file":"report.csv","id":"1","recursive":false,"title":"report.csv"},"kind":"hudson.plugins.doclinks.DocLinksPublisher","stapler-class":"hudson.plugins.doclinks.DocLinksPublisher"}],"scm":{"value":"4"}}
Environment:
OSX Mountain Lion, Firefox browser
Project:
Jenkins
Priority:
Critical
Reporter:
Peter Florijn
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15312) maven installation settings get lost
sakkew commented on JENKINS-15312 maven installation settings get lost I worked around this by overriding jenkins/tools-folder and jenkins/hudson.tasks.Maven.xml from another setup and then restarting Jenkins. If you save Jenkins config even without doing any changes, the file hudson.tasks.Maven.xml gets reset, and maven is not found by builds anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12908) TFS errors during get operation do not fail the build
redsolo commented on JENKINS-12908 TFS errors during get operation do not fail the build What kind of problems did it miss? If I have the incorrect server/auth then it will fail the build. But i guess there could be a problem with the TFS workspace if it has been moved to a new server... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15145) Unable to connect to the remote TFS server
redsolo commented on JENKINS-15145 Unable to connect to the remote TFS server Duane, Mikael has confirmed that his problem was related to user access issues when the service was run as the System local user. Could it be the same problem for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9767) MavenTestDataPublisher is unusable in this state
Ryszard Perkowski edited a comment on JENKINS-9767 MavenTestDataPublisher is unusable in this state I just created a pull request https://github.com/jenkinsci/jenkins/pull/574 with Sebastien's changes. Hope they'll get pulled in. I'm also affected by this bug in JUnit Expected Diff Plugin (https://github.com/usultis/junit-expected-diff-plugin). With provided patch it works ok. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown updated JENKINS-14932 Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (29/Sep/12 3:54 PM) Description: Instead of relying on The Timestamper plugin currently inserts a console notes, store note into every line of the timestamps in a more compact and human-readable format build's log file . The [ console Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time.Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages:- They increase the file size of the log.- They make the log file more difficult to read in a text editor.- External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not as much of a concern.)- They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest.It would be nice to store the timestamps as in a separate file to the number of elapsed milliseconds since the build started console, and in a more efficient format . The Timestamper plugin would still need a way to replace insert these timestamps when Jenkins displays back into the console log. This may require changes to when it is being viewed in Jenkins core .Backwards compatibility:* The Timestamper plugin should to retain the ability to display existing console notes.* There should be an option to still use console notes, because a few people have written scripts to read them from the log file. * The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14619) Matrix problem with Parameterized Build
cjo9900 commented on JENKINS-14619 Matrix problem with Parameterized Build Pull request on SVN plugin to complete the changes https://github.com/jenkinsci/subversion-plugin/pull/20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown updated JENKINS-14932 Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (29/Sep/12 4:09 PM) Description: The Timestamper plugin currently inserts a console note into every line of the build's log file. [Console notes|http://javadoc.jenkins-ci.org/byShortName/ConsoleNote] are a feature supported by Jenkins. They allow the timestamps to be formatted at the time the console is viewed, rather than the time that the build was running. Any alternative solution also needs to support formatting at view time.Inserting a console note into every line, as the Timestamper plugin does, has several disadvantages:- They increase increases the file size of the log .- They make file and makes the log file more difficult to read in a text editor. - External scripts may need to skip over the console notes when reading the log file. (Jenkins itself and the Jenkins plugins already need to deal with console notes, so they are not as much of a concern.) - They make it difficult to read the times with a script, e.g. to determine which parts of the build are the slowest. It would be nice to store the timestamps in a separate file to the console, and in a more efficient format. The Timestamper plugin would still need a way to insert these timestamps back into the console when it is being viewed in Jenkins.Backwards compatibility:* The Timestamper plugin should to retain the ability to display existing console notes.* There should be an option to still use console notes, because a few people have written scripts to read them from the log file.* The /timestamps URL (introduced in version 1.3.2) must continue to read the console notes when this option has been selected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13844) "Emulate clean checkout by..." does not work with 1.7 subversion repositories
Chris Lee commented on JENKINS-13844 "Emulate clean checkout by..." does not work with 1.7 subversion repositories This is caused by changes in SVN 1.7 relating to ignored files - they are no longer reported by default in 'svn status' (the SVNKit API used by Jenkins mirrors this behaviour). In the workspace for a Jenkins project (after the job has run), no changes are shown: [root@devemr01 UTIL_TRUNK]# svn status However, the below command shows files/directories that are marked as ignored: [root@devemr01 UTIL_TRUNK]# svn status --no-ignore I .gradle I build ...and creating a new file that isn't ignored shows up in 'svn status': [root@devemr01 UTIL_TRUNK]# touch foo [root@devemr01 UTIL_TRUNK]# svn status ? foo UpdateWithCleanUpdater.java needs to explicitly request that SVNKit include 'ignored' files such that they can be deleted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15360) Calendar URL changes from public to private
Justin T created JENKINS-15360 Calendar URL changes from public to private Issue Type: Bug Assignee: al_xipe Components: google-calendar Created: 29/Sep/12 5:07 PM Description: Jenkins ver. 1.483 Google Calendar plugin version 0.4 For example, this URL http://www.google.com/calendar/feeds/3aijrqcp6bftmsen9ddhobmra8%40group.calendar.google.com/public/full becomes http://www.google.com/calendar/feeds/3aijrqcp6bftmsen9ddhobmra8%40group.calendar.google.com/private/full Note the change from "public/full" to "private/full". Then, in my failed Console Output: ... GCal: Preparing calendar update request... ERROR: GCal: Could not authenticate user ... http://www.google.com/calendar/feeds/3aijrqcp6bftmsen9ddhobmra8%40group.calendar.google.com/private/full Project: Jenkins Priority: Major Reporter: Justin T This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13844) "Emulate clean checkout by..." does not work with 1.7 subversion repositories
Chris Lee
commented on JENKINS-13844
"Emulate clean checkout by..." does not work with 1.7 subversion repositories
Code from UpdateWithCleanUpdater.java:
clientManager.getStatusClient().doStatus(local, null, SVNDepth.INFINITY, false, false, true, false, new ISVNStatusHandler() {
public void handleStatus(SVNStatus status) throws SVNException {
SVNStatusType s = status.getContentsStatus();
if (s == SVNStatusType.STATUS_UNVERSIONED || s == SVNStatusType.STATUS_IGNORED || s == SVNStatusType.STATUS_MODIFIED) {
listener.getLogger().println("Deleting "+status.getFile());
try {
File f = status.getFile();
if (f.isDirectory())
hudson.Util.deleteRecursive(f);
else
f.delete();
} catch (IOException e) {
throw new SVNException(SVNErrorMessage.create(SVNErrorCode.UNKNOWN, e));
}
}
}
}, null);
...the fifth parameter is 'includeIgnored' which is strangely set to false (and always has been), although the subsequent code expects ignored elements. Guessing that the inclusion of 'ignored' files was a bug with previous SVN (and SVNKit) versions that Jenkins inadvertently relied on.
SVNKit API: http://svnkit.com/javadoc/org/tmatesoft/svn/core/wc/SVNStatusClient.html#doStatus(java.io.File, org.tmatesoft.svn.core.wc.SVNRevision, org.tmatesoft.svn.core.SVNDepth, boolean, boolean, boolean, boolean, org.tmatesoft.svn.core.wc.ISVNStatusHandler, java.util.Collection)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks started work on TEST-32 test Change By: David Sheeks (29/Sep/12 7:58 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks created TEST-32 test Issue Type: New Feature Assignee: David Sheeks Components: test2 Created: 29/Sep/12 7:58 PM Description: taest Due Date: 29/Sep/12 12:00 AM Environment: test Project: test Priority: Major Reporter: David Sheeks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks stopped work on TEST-32 test Change By: David Sheeks (29/Sep/12 7:58 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks closed TEST-32 as Fixed test Change By: David Sheeks (29/Sep/12 8:00 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3715) Resource filtering fails when run from Hudson
Zachary Young commented on JENKINS-3715 Resource filtering fails when run from Hudson I'm seeing this behavior, too. Is this considered a "non"-issue, now? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-33) test2
David Sheeks created TEST-33 test2 Issue Type: New Feature Assignee: David Sheeks Components: test2 Created: 29/Sep/12 8:15 PM Description: dfds Environment: dfdf Project: test Priority: Major Reporter: David Sheeks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-33) test2
David Sheeks assigned TEST-33 to David Sheeks test2 Change By: David Sheeks (29/Sep/12 8:16 PM) Assignee: David Sheeks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-33) test2
David Sheeks assigned TEST-33 to Unassigned test2 Change By: David Sheeks (29/Sep/12 8:16 PM) Assignee: David Sheeks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-33) test2
David Sheeks resolved TEST-33 as Fixed test2 resolved Change By: David Sheeks (29/Sep/12 8:20 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-33) test2
David Sheeks reopened TEST-33 test2 Change By: David Sheeks (29/Sep/12 8:25 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14840) default graph values are not saved
evernat updated JENKINS-14840 default graph values are not saved Change By: evernat (29/Sep/12 9:03 PM) Description: With a fresh install of Jenkins 1.477, the following plugins are installed:Static Analysis Utilities (1.43),FindBugs Plug-in (4.42),Warnings Plug-in (4.13),Checkstyle Plug-in (3.29),PMD Plug-in (3.29),Task Scanner Plug-in (4.32),Static Analysis Collector Plug-in (1.29).In a maven job, a combined analysis is configured.Then in the default graph configuration (job/test/analysis/configureDefaults/?), whatever values are written they are not saved when clicking the save button.There is no error displayed in the browser or in the logs.The lastModified tome time of the analysis.txt file in the job directory is changed when clicking the save button, but the content is always the same (500!200!50!30!PRIORITY!0).Tested with both firefox and chrome. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14840) default graph values are not saved
evernat commented on JENKINS-14840 default graph values are not saved Yes, the default graph values are saved for the other plugins, the tasks and findbugs plugins for example. At least, after the first build with the plugins enabled. But it does not work for the default graph values of the combined analysis. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-30) testing #2
David Sheeks commented on TEST-30 testing #2 dd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-30) testing #2
David Sheeks closed TEST-30 as Fixed testing #2 Change By: David Sheeks (29/Sep/12 10:01 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-30) testing #2
David Sheeks reopened TEST-30 testing #2 Change By: David Sheeks (29/Sep/12 10:05 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13279) Interface with Crowd embedded that runs in Jira
Jeffrey Damick commented on JENKINS-13279 Interface with Crowd embedded that runs in Jira jenkins: 1.482 crowd2: 1.5 When i configured it against my embedded crowd in jira, jenkins just gives 500s over and over, and logs this: WARNING: Untrapped Error in Servlet java.lang.IllegalArgumentException: The validated object is null at org.apache.commons.lang.Validate.notNull(Validate.java:222) at com.atlassian.crowd.integration.http.util.CrowdHttpTokenHelperImpl.getCrowdToken(CrowdHttpTokenHelperImpl.java:39) at com.atlassian.crowd.integration.http.CrowdHttpAuthenticatorImpl.logout(CrowdHttpAuthenticatorImpl.java:184) at de.theit.jenkins.crowd.CrowdRememberMeServices.logout(CrowdRememberMeServices.java:275) at de.theit.jenkins.crowd.CrowdServletFilter.doFilter(CrowdServletFilter.java:154) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks updated TEST-32 test Change By: David Sheeks (30/Sep/12 1:20 AM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks started work on TEST-32 test Change By: David Sheeks (30/Sep/12 1:20 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks reopened TEST-32 test Change By: David Sheeks (30/Sep/12 1:20 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks stopped work on TEST-32 test Change By: David Sheeks (30/Sep/12 1:20 AM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-32) test
David Sheeks commented on TEST-32 test test This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
