Petter Gonçalves Atlassian Team

Hello Stian, Actually, JIRA Service Desk is only an Add-on that runs in the JIRA Core application. That being said, the API call to create a new issue is the same on both applications, as if you were creating an internal issue and then adding the request type as you mentioned. Please, refer to the documentation below to…

 Hello Sébastien, - For custom field translations, you can check the table entity_translation - For Statuses translations, you can check the properties tables, as mentioned by @Nic Brough -Adaptavist- in this post:…

Hello Jia, Unfortunately, there's no way to Bulk change the Request Type of issues as you need using JIRA Cloud. The option available is only applied to JIRA Server. Please, feel free to watch and vote on the reported feature request below: - Bulk Update Request Type Configuration

Hello Unnati, You can use the plugin Automation Lite For JIRA (Free for 300 executions per month) to achieve this functionality with a simple rule:

Hello Jade, Can you provide us a screenshot of the place that you would like to remove the Priority, Time Tracking & Time Estimate fields?

You are welcome, Sourav.

Hello Linda, I understand that you are trying to move your Stories from one board column to another, is that right? If that's the case, have you properly mapped the status of your workflow to your board columns? To do it, you can click on the three dots icon (...) > Board Settings > Columns and check if your workflow…

Hello Michael, The filter I'm using only return issues from the project related to the board too, however, it still displays the Epic name on the board. That being said, I believe that maybe your filter sharing or any other specific configuration of the filter can be blocking you from seeing the Epic links since it has…

Hello Michael, Thank you for your answer. Testing the behavior you described, the Epics from different projects linked to my issues are properly displaying on my board. The Epic Testing Epic 2 is properly displayed on my board although it is from a different project (SD2), as you can see below: That being said, I started…

Hello Sourav, In JIRA, the best free functionality that you can use to achieve this would be: - Create a date/time custom field - Add the field to the screen in the In review transition - Configure a post function in the In review transition that will automatically fill the custom field with the current date when the…

Hello Michael, Can you please provide us a screenshot displaying where the Epic name is appearing exactly in Project A? There are several places and possible features on JIRA board that can display Epics, I just need to see where is the place you are referring.

Hello Pooja, Since you are configuring a rule that will be applied to multiple projects, you will need to create a Global Rule by clicking on the Global Administration link: Please, create the same rule, but using that option and let me know if it works. P.S: Sometimes the Automation can take some time to finish (1 minute)…

You are welcome, Max. 

Hello Arjun, There are several ways to handle feature requests using JIRA. I can recommend you the following ones: - Create a new request type on your SD project to create feature requests, OR - Create a new SD project to only handle feature requests Using one of both options above, you will be able to better organize and…

Hello Max, Actually, the change of the order in the filter of the board (Not the Quick filter, but the own board filter) does affect the backlog too: Check that my issues on the backlog are ordered by issue key: Once I changed the board filter, It becomes organized by issue type:

Hello Orazio, Here are the steps: - Navigate to your JIRA > JIRA Settings > System > External System Import OR - Type GG > Type External System Import - Click on CSV and follow the steps of the Client to import your excel file and properly map the fields on your CSV and create JIRA issues P.S: If you have any questions…

Hello Liam, You can order your Backlog and Sprint Stories as you need by using the command ORDER BY in the JQL filter of the board: - Navigate to your board > Click on the three dots icon (...) > Board Settings - Click on Edit Filter Query > Add the parameter ORDER BY + the field you want to your filter and save. E.g:…

Hello Pooja, You only need to use a Branch rule to determine the status of the linked issue: Please, let me know if it works for you.

Hello Musku, Unfortunately, this kind of customization is not available natively on JIRA, however, you can use the following add-on to do it: - Clone Plus for Jira

Hello Justin, You're correct. As you can see in this Documentation, Request Participants are considered customers who watch requests and can provide more information about it. That being said, they are considered as customers when we talk about Automation Rules too.

Hello Saket, Could you please provide us a screenshot of the screens in the Old and new View? Also, Are you using JIRA Cloud or JIRA Server? In my instance, the edit button to change the issue type is working just fine in the new issue view: Please, provide us with your JIRA version so we can better understand your problem.

You are welcome, Olivier. Please, let us know the feedback of Adaptavist.

You are welcome, Tawhid.

Hello Tawhid, Are you using JIRA Server or Cloud? If you are using JIRA Server, you can try the free add-on Jira Status Color or Color Custom Fields. If you are using JIRA Cloud, I'm afraid that this is not possible at this moment, as you can see on this discussion:…

Hello Narasimha, Unfortunately, all the created add-ons to perform this kind of change are only available for JIRA server, however, JIRA Cloud has an import/export functionality where you can optionally perform in different formats and it's completely free. The most simple format to perform it is by using CSV (Excel)…

Hello Ken, The behavior you informed about the New Issue View is being reported and treated as a bug by our Atlassian Developers: - Wiki Markup does not work in the New Jira Issue View That being said, we are currently working to fix it and is unlikely that our development team are going to disable you from the old version…

Hello Orazio, To import issues to an existing Epic in your JIRA, you only need to add an extra column to your Excel with the Custom field (Epic Link) and map the issuekey of the Epic on the column. E.g: assignee, summary, description, Created date, Custom field (Epic Link) user, test, testing issue, 21/sep/2018,…

Hello Phani, The functionality you are looking for can only be achieved by Scripting using the ScriptRunner plugin and configuring a condition like the one below: - if ("Done".equals(issue.getParentObject().getStatus) ) { return false } For more reference, you can check the discussion below and the documentation od…

Hello Fawad, There are some options that you can use to achieve this functionality. Basically, you can use two plugins: JIRA Misc Workflow Extensions or ScriptRunner Please, check the discussion below to have more details about it:…

Hello Paolo, There's no way to do it natively with JIRA Cloud, however, you can use the add-on Scriptrunner which provide you the issuefunction parameter, so you can configure a Script like the one below to return the issues you need: issueFunction in linkedIssuesOf(“issuetype = Epic and status = Open") Also, Atlassian has…