JQL configuration in Linux

[Sriram Subramanian]

Team,

whats the purpose of the jar "jql-scheduler-0.1.0.jar" ? is this required to be installed for using jql in the jira filters? I have my jar file installed in my dev box and have created new mounts to be used, 2 things wihch I need to know

1. Whats the purpose of that jar "jql-scheduler-0.1.0.jar"? is this the main source for jql to be used in jira filters?

2. If i need to change the scheduler path from one to another, how do I update it? 

sorry that am new to jira and trying to understand the gaps. Appreciate if you can advice how to insall the jar and update the jql path from one to another? 

Regards

Sriram S 

[Kinto Soft · Accepted solution]

Hi Paul,

It is not possible to delete any commit in Subversion. So, the plug-in is working fine.

For example: If you create a version of an artifact X in the revison N with the comment "blah, blah, blah TEST-1 blah, blah" and then you delete it the revision N+1, it will still be shown in the issue page , related to the revision N.

That is because the plug-in gets the full history of the whole repository (for all the versioned artifacts) and X@N is part of the history, even it was deleted in X@N+1

Hope this helps,

Pablo.

[Paul Jones]

Had a suspicion this might be causing the problem; certainly sounds like it is what we're seeing. For one project to have a few test comments isn't the biggest problem in the world.

Thanks for the clarification.

[JohnA]

Hi Paul,

It sounds like your SVN plugin's index directory has been corrupted, but once you have deleted the index and restarted the application the index will be recreated and the deleted commits should no longer show. So, to do this please perform the following steps:

1. Delete the $INDEXDIR/plugins/atlassian-subversion-revisions directory
2. Restart JIRA.

All the best,
John

[Paul Jones]

Hi, thanks for the reply.

So I have tried this, deleting both the atlassian-subversion-revisions directory and everything beneath $INDEXDIR with a forced reindex after logging back into jira. Comments are still showing.

So that's stop jira, delete the directory, start jira, force/wait for a reindex. You can see the reindex happening because there are no comments immediately after login then they reappear after the index has happened. But unfortunately too many of them :-)

If that's the process though for resyncing the plugin with the repos, then it suggests the comments actually haven't been deleted from the svn properly. Might be worth me re-checking there just in case.