Change displayName for Jira System User 'Scriptrunner' on Jira Cloud - jira

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.

Related

Bug Tracking Tools that Push to Jira

Our dev team uses Jira for our user stories. However, our clients don't have access to our Jira account. I am looking for a bug tracking tool that the clients can access and can sync/push the bugs they log into Jira. Does such a tool exist?
I found a good option with the tool ReqTest. Looks like there is a plugin for Jira that allows you to sync issues.

How to get all the available email handlers in jira?

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.

JIRA Integration with external systems

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.

Email notification when using system monitoring

I am doing a Grails project. And here are some requirements about the system monitoring as below:
1. Email notify team when system goes down
2. Email notify team system log daily
3. Email notify team when app is deployed
So I don't know what to meet my requirements.
Could someone help me?
Use any monitoring software or service. I use New Relic, but there are plenty to choose from. If you only need ping, use a ping monitoring service. I use a free Google script I found on the Internet, but it has had some false alerts.
Use the Quartz plugin to send the log at a daily basis, or a cron job or similar.
Maybe use a shell script that does the employment and sends an email as well, or it might exist a Grails event for deployment.

Why does the JIRA User for the Rally Jira Connector have to be a JIRA Administrator?

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.

Resources