I am writing a java plugin for jira and I am require to list the mail handlers currently active in jira. How can I do so?
I am unwilling to hit Database.
Related
We use Jira Cloud at my company and we also use 'ScriptRunner' as a plugin for running useful scripts to automate tasks.
When actions are performed by this user the displayName is "
ScriptRunner for Jira" and I'd like to change it to "IT Department".
Because of deprecation from Atlassian on the REST API it doesn't seem possible to change the displayName. Yet again another example of deprecation of Jira Server being a nightmare.
I can't find any way to rename a system user.
I'm working on a POC to automate downstream processes in external systems based on JIRA processes and have hit a wall with the API. It appears to have great integration for pulling data about tickets out of JIRA and for the ability to externally generate tickets into JIRA.
However I don't see how to trigger external calls as a part of my workflows. For example if a ticket should be prevented from being routed to the next stage of a workflow without accessing a database to ensure availability of inventory first how could I do that in JIRA?
Based on attributes in the JIRA ticket upon final completion of the workflow we'd like to send a JMS or REST message or possibly update an external database. Is this possible?
Thanks all in advance for the help!
If you want to do a "before" check, use a Validator on the Workflow Transition.
I strongly suggest deploying the (free) Script Runner add-on. There you can implement a ton of things. For example, you'll get a new validator option "Script Validator", where you can specify a Groovy script that decides if it lets through the transition or aborts it.
The Jira integration is mentioned in http://splunkbase.splunk.com/apps/All/3.x/Operations/Change_Management/app:Splunk+for+Jira
I see that you can submit bugs to Fogbugz via HTTP Post.
In Splunk there is a feature called Workflow actions.
And you could use this to HTTP Post a bug to Fogbugz in response to certain event types or presence of certain fields.
I've been asked to look at configuring the Rally JIRA Connector to synchronise Rally with our JIRA instance and the installation instructions state that the user you create in JIRA has to be a JIRA Administrator. Why does it need admin permissions when all it appears to be doing is updating the RallyID and RallyURL custom fields for issues in the JIRA project(s) synching with Rally.
Are edit permissions for issues on the project not enough, or is it doing something else that requires admin privileges? I did remove the user from the jira-administrators group, but the connector checks for administrator privileges and halts if the user is not an admin.
If the user does not need admin privileges is it possible to alter/remove the check in the connector so that the user can be removed from the jira-administrators group and just be given the relevant permissions in JIRA?
Thanks,
Andrew.
it's a 2 part answer:
The connector runs a validation step on your config file to verify that all of the fields you have mapped do exist in Jira. Historically, with earlier versions of Jira out of the box, only the administrators group had permissions to get that list of fields on issues.
If you are using a field handler to transform in users to Jira, we again needed higher level permissions to get the list of users in Jira - eg to do a lookup based on email.
Hope that information helps.
We are moving from Mantis to JIRA and wish to keep Mantis alive for some time until the migration is complete and all the users are migrated.
All users (esp. the dev team) that have been migrated to JIRA shouldn't continue with Mantis (maybe deactivate accounts) and concentrate on JIRA alone.
Thus if a Mantis issue that was migrated to JIRA gets fixed/commented (in JIRA) the new status should be synchronized to the still existing Mantis issue.
And (if possible) new issues that are created in Mantis should be automatically be added to JIRA (if this is not possible then thats OK too)
Does anybody know of a tool or plugin that can do this?
I do not know any tool that does it, but in our company we have successfully implemented sync tool for Jira<->Footprints and Jira<->CRM. It would use Jira SOAP API (or REST starting from 5.0) and Mantis SOAP API. This tool can regularly check issues in both systems and update them accordingly.
Jira SOAP API - http://docs.atlassian.com/software/jira/docs/api/rpc-jira-plugin/latest/index.html?com/atlassian/jira/rpc/soap/JiraSoapService.html
Jira REST API - https://developer.atlassian.com/display/JIRADEV/JIRA+REST+APIs
you can implement your own sync using Jira's REST API as #Daria replied above, or you can use Task Adapter for manual data synchronization between Jira and Mantis.
Sorry I have no immediate answer, but we are developing an internal tool for exactly this purpose:
migrate existing issues from Mantis -> JIRA
ability to enter new issues in Mantis and have them synced to JIRA
activity in JIRA issues replicated back to Mantis
workflow disabled in Mantis (issues are slaved to JIRA state)
keep Mantis alive for N months while users are trained and migrated
It is using their SOAP and REST APis respectively.
If there is interest and it works well (looking really good at this stage) I will seek permission to open source it.