I've 847 Projects in Jira 3.13.5. Now i want to clean it. I want to backup and delete all Projects, which haven't any activity in 2012. But how can I check that?
Using JIRA SOAP API:
Get all your project keys using getProjectsNoSchemes method.
To find out the most recently updated issue from each project, iterate over all of those keys and run:
jiraSoapService.getIssuesFromJqlSearch(authToken, "project = " + projectKey + " ORDER BY updatedDate", 1);
Note the 1 as the last argument - this limits the JQL result to only 1 issue, since we order the query by updatedDate this gives us the single, most recently updated issue from given project.
Just check if updatedDate of that issue is below 2012-01-01 and you've got your answer.
Here's javadoc for JIRA SOAP API: http://docs.atlassian.com/rpc-jira-plugin/latest/com/atlassian/jira/rpc/soap/JiraSoapService.html
Here's a tutorial on how to create a JIRA SOAP client: https://developer.atlassian.com/display/JIRADEV/Creating+a+JIRA+SOAP+Client#CreatingaJIRASOAPClient-Step2.CreatetheSOAPclientproject
EDIT: Sorry, just realized that JIRA 3.13 doesn't have JQL searches yet so the answer is not valid for this JIRA version.
Related
I updated PHP 5.6 to 7 and MySQL 5.5 to 5.7.
Everything was fine in the older versions, however since I updated the server some plugins such as: Custom 404 page, gregorian2jalali face problems. Some pages goes blank and the Inspect Element, Console section nothing shows. up. For example, if I activate gregorian2jalali plugin, User Profie page doesn't show up.
Also in the Custom 404 page plugin, the following error comes up in 404 pages:
A Question2Answer database query failed when generating this page. A full description of the failure is available in the web server's error log file.
There was a related question for an earlier problem here: When adding page link, database query error occurs.
In the Apache Error Log, a message similar to this message comes up:
PHP Question2Answer MySQL query error 1146: Table 'qa.qa_options' doesn't exist - Query: (SELECT 'options' AS selectkey, title, content FROM qa_options) UNION ALL (SELECT 'time', 'db_time', UNIX_TIMESTAMP(NOW()))
Also, there was an earlier problem here at this question: is there a way to manually create the database tables ?
Now that the plugin is not updated, how I can fix this problem ?
Thanks
Q2A version: 1.7.4
There are two possibilities I can think of:
You are using a different table prefix (e.g. abc_ instead of qa_) in your qa-config.php file, and a plugin is putting qa_options in their SQL queries instead of ^options as they should (which automatically adds the correct prefix).
Or, you are using the unstable 1.8 version from GitHub which currently has a few issues regarding plugins. If so, make sure you're using the stable 1.7.4 version that you get from the main Q2A site.
When trying to check a change into TFS with TEE (v14) I get an error if I try and select a query. The error is,
Unable to run query
The query "My Work Items" can't be run because of the following error with the query:
The specified variable does not exist. The error is caused by <<#project>>.
This is environmental though as I have another VM which is perfectly fine but uses a slightly old eclipse (Kepler). This to me implies that actually there is nothing wrong with the query!! I have compared the configuration in .microsoft but with no joy.
I can check in by using the task ID directly but would like to be able to see my tasks. Any help would be really appreciated.
Thanks,
Andy
Redhat 6.7
Eclipse Luna (4.4.2)
TEE Plugin v14
There is a bug in current version Team Explorer Everywhere 2015 (14.0.1) which causes the "specified variable does not exist" error message.
As a workaround, you can either: 1) run the query prior to opening the "Check In" dialog, or 2) add the work item to the dialog by entering its ID.
(check David Staheli's post in the bottom of this blog: http://blogs.msdn.com/b/bharry/archive/2015/07/06/team-explorer-everywhere-2015-rtm.aspx)
First, after I updated the Cloud SQL Admin API via Eclipse, I noticed that some of my classes broke. Apparently the API had changed.
Specifically, methods in ExportContext had changed; setDatabase() was no longer present and had been replaced by setDatabases() and setTable() had been replaced by setSqlExportOptions().
BUT, the problem is, after updating my code to the new API, it won't run.
New Code:
ExportContext exportContext = new ExportContext()
.setFileType("SQL")
.setDatabases( Arrays.asList(srcDatabase) )
.setSqlExportOptions( new SqlExportOptions().setTables( new ArrayList<String>(tableNames) ) )
.setUri(dumpUri);
Here is the exception:
(com.google.api.services.sqladmin.model.ExportContext.setFileType(Ljava/lang/String;)Lcom/google/api/services/sqladmin/model/ExportContext;)
java.lang.NoSuchMethodError: com.google.api.services.sqladmin.model.ExportContext.setFileType(Ljava/lang/String;)Lcom/google/api/services/sqladmin/model/ExportContext;
How can i fix this?
The new version of the Cloud SQL Admin API, v1beta4, was recently released and it includes a few changes like the ones you are saying. For example setSqlExportOptions needs to be set for exporting data in SQL format.
The old version, v1beta3 is still available. My guess is that you never specified an API version and eclipse automatically generated the client code for the latest version. Make sure you specify which version you want to use.
I'm trying typesafe stack.
Yesterday, I can get project template of typesafe stack.
$sudo g8 typesafehub/akka-java-maven
Today: I can't get project template.
$sudo g8 typesafehub/play-java
Error:
Exception fetching from github Unexpected response code: 403
{"message":"Missing or invalid User Agent string. See http://developer.github.com/v3/#user-agent-required"}
I think that github have changed their API rules.
I have seen a similar problem cited by someone using telegr.am .
I will try to have a look at how to control the user agent sent, if I get a chance today.
Only sorry to not have a complete solution for you straight away.
As a workaround:
1. Clone the github repo into your computer
2. Upgrade to the latest giter8 ( see https://github.com/n8han/giter8/blob/master/notes/0.5.0.markdown)
3. Check where the new giter8 has been installed, for me it was /home//bin/g8
4. Execute the local template with the new giter8
/home/<username>/bin/g8 file://home/<username>/path/to/the/template.g8
I haven't found any clear information about this around.
Is it possible to integrate the sourceforge tracking system for bugs/features with Mylyn?
I've found this page that seems a bit old (indeed the link for downloading the general connector does not work).
Anyone have a clue about this? It is possible to realise such a kind of connection?
Yes with the move of SourceForge to use Allura the configuration on the page you highlighted is outdated.
I posted details on getting the Web Template Connector to work for Allura at http://officefloor.wordpress.com/2012/12/10/allura-sourceforge-mylyn-connector/
The generic connector is now in the Mylyn incubator. Use this download site:
http://download.eclipse.org/mylyn/incubator/3.7 (for Eclipse 3.6, 3.7, 3.8)
Since I wasn't able to get it running – maybe it's because of Eclipse Luna or something else – I slightly modified Daniel's method which partially uses the REST interface:
Basic Configuration
Add the following parameters and appropriate values to the table unter Additional Settings section in the Properties for Task Repository dialog:
project – your so-called UNIX name of the project
tickets – the ticketing application, e.g. bugs or features
bearer_token – you need to set-up a bearer token as described in the Allura documentation
under Advanced Configuration, use:
Task URL: ${serverUrl}/p/${project}/${tickets}/ (the same as in Daniel's method)
New Task URL: ${serverUrl}/p/${project}/${tickets}/new (the same as in Daniel's method)
Query Request URL: ${serverUrl}/rest/p/${project}/${tickets}?access_token=${bearer_token}
Query Pattern: \{"summary":\s*"({Description}.+?)",\s*"ticket_num":\s*({Id}.+?)\}
Milestone query
To query tasks by milestones, use the following parameters in your Edit Query configuration:
add a parameter milestone with e.g. M1 to the parameter table
use the following Query URL: ${serverUrl}/rest/p/${project}/${tickets}/search?q=_milestone%3A${milestone}&access_token=${bearer_token}