Ravi Sagar _Sparxsys_ Expert

Hi @Niall McCaffrey Why not just update the page with some text and remove it in the next call? Ravi

Hi @Hila Armoza As @Medhat Ahmed the most simplest way is to create a custom field is that is all you need to track. Depending upon the size of your project you can also have customer specific projects but it seems like you will be fine just a custom field. It will help you later with reporting as well. To link User Story…

Hi @Анастасия Герасимова Take a look at this page as a starting point but @Nic Brough -Adaptavist- mentioned start by your requirements first and see which one out of cloud or DC is suitable for your requirements. Ravi

Very nice. Well if it works then all good. Just add some error handling for null values but overall looks good.

Hi @Ha Tran The default screen has most of the common system fields. There is real disadvantage of using it but most likely you would have your own set of fields in your issue type (and project) and you may not want to use all the system fields for all the cases. In any case Jira gives you flexibility to modify the…

Hi @Tracy Stahl Yes you should be able to do that. For more details and future reference do take a look at this page: https://confluence.atlassian.com/doc/upgrading-confluence-4578.html#UpgradingConfluence-1.Determineyourupgradepath I hope it helps. Ravi

Hi @Bakiyaraj Periyasamy Take a look at the Long Term Support Releases from Atlassian on this page: https://confluence.atlassian.com/enterprise/long-term-support-releases-948227420.html Ravi

Hi @norair.markarian If you have those boards with issues/tickets from the same project then you don't really need to move hem anywhere. Just reconfigure the board settings. You can configure the filter for your board that will ensure that the issues will show up in the board you want. Ravi

Hi @Feroz Basha S Yes you can do that using REST API using the following end point. Endpoint: GET /rest/api/3/issue/KEY-123 In the JSON you will find an attachment section. How are you doing the integration to salesforce? using your own code or interface? If yes then yes you can access the attachments using the end point…

Hi @Pavan Chiti You would need an app like ScriptRunner, it has a behaviour functionality which can let you add this dynamic features on the create issue screen. Take a look at some sample scripts as well. Ravi

Hi @Marko Majkic I also wish if JQL could do inner joins :) JQL consists of multiple queries and each query returns issues. Try some of these apps for improving the JQL search. Ravi

Hi @Ganesh As @Nic Brough -Adaptavist- mentioned you need to create a custom event (or existing one) and configure your notification scheme to use that event and specific who will receive an email. I explain exactly how to do this in this video here. I hope it helps. Ravi

Hi @Jelmer Dijkstra If you want to follow an order in which activities should be done then I believe the best way would be to rely on the workflow to trigger those sub task creation. Open > stage 1 > stage 2 > stage 3 and so on That's the whole point of having a workflow, to follow a processes. Imagine when the issue is…

Hi @Udhay Kiran As @John Funk mentioned doing it using Automation is probably the simplest method. Other options. * Create a job using ScriptRunner since you mentioned Scripting. * You can use REST API to do it using your own script that you can run from outside Jira, may be by configuring a cron job. I hope it helps. Ravi

Hi @Mahima Sagarika Rajendran Well you can do csv import or use REST API to do it. Make sure the field is present in the target project issue type screens with applicable context. Ravi

Hi @VGS Register Where are those users stored if they are not assignee? Ravi

Hi @anthony_tzvetkov You can do it yourself by going to https://my.atlassian.com/ Ravi

Hi @Manon Ledda This is a common use case. The suggestion here would be to not move the ticket, instead create a linked ticket. Move ideally should be used when issue/ticket was created by mistake in wrong place. Using linking feature you will have traceability and later on can report on issue that required other team's…

Hi @Alex Smith I will ask someone to look at it. Do you have a link to apply or your contact? Ravi

Hi @Nate Rothstein Trying to understand your requirements. Do you want to reuse a custom field in multiple projects? or do you want to have project specific options in a custom field? Ravi

This is brilliant 👍

Hi @Mandeep Khaira There is a already a feature request for this https://jira.atlassian.com/browse/JRACLOUD-8092 I suggest you vote for it. I will do that too. I think it would be useful. Ravi

Oh yes there is already a feature request for it but I am not sure if Atlassian will do it.

Hi @DeAnna Law This is a very common question that people ask, field level permission is not a feature in Jira natively. What you can do however is use the workflow instead. * You can create a transition in your workflow * Show a transition screen with the field you want to capture from specific role * Use workflow…

Hi @Damian Munday Go to your board settings and modify the filter query to not include specific issue types. Ravi

Hi @fereshte kh Without an app it is difficult to achieve but what you can do is that whenever an issue is assigned to a user you can create an automation rule to know how many other issues are already assigned to that user using something like this. {{issue.assignee.displayName}} already has {{lookupIssues.size}} assigned…

Hi @Aravind Gopalakrishnan Apart from checking the source as @David Wuth mentioned also check if there are any filters applied or not on your current plan view. Ravi

Hi @Nicole Millot You can do this with the help of ScriptRunner for Jira. You can create a Script Field to display current user's groups on Jira issue using something like this. ComponentAccessor.getGroupManager().getGroupsForUser(userName) This is just a code snippet, not full code but easy to achieve. I was wondering why…

:) I am glad it was useful.

Hi @Pushkar Padmanabhuni What exactly are you trying to achieve? Do you want to restore your Jira instance or migrate it to another server or move to Cloud? Ravi