Ravi Sagar _Sparxsys_ Expert

Hi @Aaron Korb Why not write your own code using ScriptRunner for Jira and use custom REST End points? Ravi

Hi @[deleted] Probably not. Not everyone in your organisation will be working on all the projects. * Each project can have a Project Lead and that person can manage their own team by adding people to different project roles * Project roles developer, tester, etc are like teams * What these project roles can do in the…

Hi @Scott Thurston Have you tried the Message Custom Field (for view)? Ravi UPDATE: This field will only appear on Issue View. So I think you can just rename your field to something like "Review Fields", so it is clear for the user. So you can use the Message Custom Field (for edit) instead.

You will get CSV which you can open in Excel. Use the option Text to Column with comma as the delimiter.

Hi @Cédric Cox What about if you still use the Issue Created event and in your code look for the history by expanding the changelog. /rest/api/3/issue/ESD-20?expand=changelog If the issue is created by moving then it will have this entry. { "field": "Key", "fieldtype": "jira", "from": null, "fromString": "ISD-17", "to":…

Go to the search box on top right of your Jira instance or press forward slash / and then click on Issues. 

Hi @SMT - Mustafa Demir You can use the Issue Navigator to search for the issues using the same JQL as used in your queue, there is an option there to export the issues in csv. I hope it helps. Ravi

Hi @Nick P When you resolve the issue which is I guess a status in your workflow you need to associate a transition screen to capture the information you want user to fill. The issue operations - create, edit and view are different from workflow transitions. So if I understand correctly (you can confirm) you need to modify…

@Aisha M In the behaviour mapping set choose projects to All projects and then use write script to hide the field for all projects except 5 or 6. Take a look at this script and modify it as per your needs by also checking for project.

Hi @Nicholas Power In Jira Service Desk each project will get its own portal. Although there is a help centre as well that will list all those portals. * Use different projects if you have different teams handling the request with absolutely no overlap. * Even if you create one project you will have the option to expose…

Hi @Aisha M As @Marco Brundel mentioned you should be using field configuration for that. Ravi

Hi @Gordon Rutherford Yes, you can contact us for any custom scripting and someone will get back to you. Ravi

1. Not sure how it will work when you opt out of Atlassian Access. 2. Initial setup - few days. Add few more days to customise Jira and configuring projects, SSO etc. Maintenance tasks - depends how big your instance is, but there are things like managing backups, monitoring, 1 or 2 upgrades annually and some clean up. For…

Hi @Natálie The first thing I would check is the Resolution field on those issues. Usually these gadgets don't show issues if the Resolution is set. Ravi

Hi @Gordon Rutherford It can definitely be achieved with ScriptRunner. You can take a look at various scripts related to date fields here. I hope it helps. Ravi

Hi @Abraham Assadi For Cloud you can check Atlassian access. "Internal with LDAP Authentication" is for server version of Jira. Ravi

Create separate Issue Types when you have separate process for those issues like Bug are different from Stories and when you need to capture/track different information for those activities/tasks. 

You can modify the format if you want by modifying the argument 'dd-MM-yyyy--HH-mm' Did you take a look at the example scripts on library? Take a look at this script to understand how to work with dates.

Hi @neeta jain You need to add this line on top as well. import java.text.SimpleDateFormat Ravi

Hi @Tanya W Yes custom field can work. You can then create a filter and then use that filter in various dashboard gadget to create reports based on that category field like a simple Pie Chart. Before you create a new custom field try to use Components field. Components in Jira also bring more features like auto assigning…

Hi @Sonny Swann If you look in your log file then there will be some detail about what went wrong. Log file will be in your home directory. Something like: * C:\Program Files\Atlassian\Application Data\JIRA (on Windows) or * /var/atlassian/application-data/JIRA (on Linux) Check this page to understand important…

Hi @Montana Fox Don't do that it will break things but if you really have to then take a look at jiraworkflows table in your database. Modifying database is only for rare cases when things go wrong and there is no other option. In your case bulk modifying post function and correcting typos is not a good justification. In…

Hi @dinar Releases are project specific natively in Jira unless you use an app like Advanced Roadmaps (which is now part of Cloud premium) or Release Management & Roadmap. I hope it helps. Ravi

Hi @Naglaa Reda Check if they have Browse project permission in the relevant projects' permission scheme. If this permission is assigned to a role like developer then those users should be added to that role but first check the permissions scheme. Ravi

Hi @Sam Desai Since you are on cloud this is what I can recommend. * Create a project with "HR Service Desk" template. It comes with a request type called Onboarding. This is just to give you an idea. You can either use this project or take a look at the configurations. * Once you create an issue if all the relevant fields…

Hi @Mauro Gobbi Yes continue using Epics. For phases it could be managed in your Epic workflow. Ravi

Hi @Adam Wojak Are you using the SLAs? You can configure Automation rule based on SLA breached. Ravi

Ok I understand. Take a look at this app: https://marketplace.atlassian.com/apps/1221429/historic-content-of-jira-in-confluence?hosting=server&tab=overview No sure if it is still maintained. It does what you are looking for. There are other apps that can show issue history in different ways but apart from the link above I…

You can ignore these STC errors. Also look at this page for information related to this topic: https://scriptrunner.adaptavist.com/latest/jira/#_tips_for_type_checking

Hi @Jon Schewe Did the script work in your instance? Ravi