Marc -Devoteam- Community Champion

Hi @Elif Alverson I have looked into this and the issue I haven't been able to resolve is that when automated change of the issue to Epic To have the Epic Name populated. I have tried to use the issue summary as the value of a variable and let the Epic Name be populated with value, so that on the sub-task this can be set…

Hi @Abby O_Connell You need to map issue key to the table in your CSV where the issue key is mentioned, to accomplish updating existing issues. So in you CSV you should have a column with the existing issue keys

Hi @sravani.x.battu Just change the edit action as follows, this should do the trick

Hi @Sonia You should be able to drag a sub-task to the same status. It should than rank itself above another sub-task It worked on my side in Cloud on a default Kanban project. But this only works on sub-task linked to the same parent, you can rank sub-task differently based on different parents.

But I see the following error: An error occurred while getting the access token: Error: Failed to get access token: Unauthorized So you are not authorised correctly, so this will cause the API call to fail. SO there is something wrong in the call to authenticate yourself. Could you first see if your authentication works?

Quick question, Does your test and test execution already exist in Jira (XAUTO-25 and XAUTO-4)? Or does only the Test (XAUTO-4) exists? If the call is to create a new Test Execution you should use the following api call (example): { "info" : { "summary" : "Execution of automated tests for release v1.3",…

Hi @Anmol Fattepur I see this: const testExecutionData = { info: { "testExecutionKey": "XAUTO-25",For me this seems to be:const testExecutionData = { "testExecutionKey": "XAUTO-25",And at the end],This should be just ]

Hi @Abby O_Connell Yes, if you need to be admin to achieve an import to update issues, otherwise just new issue will be created on an import.

Hi @Kinka Family IT Quick and maybe simple questions from my side * Is the Field Brands mandatory on issue creation? * Would you be able to share a screenshot of a created issue? If all above is correct and an issue has a value for the Brand field. I would suggest you to add the edit action: Re-fetch issue data, before the…

Hi @Anmol Fattepur If I look at your input { info: { testExecutionKey: 'XAUTO-25', summary: 'Execution of automated tests for release v1.3', description: 'TEST!!!! This execution is automatically created when importing execution results from an external source', version: 'Beta', user: 'Anmol Fattepur',…

@LAL "Is there a way to easily reuse tests between projects or am I stuck manually exporting/importing/copying tests one by one?" In your case only export and import will do the trick, as there is no such function in Xray. After the export, edit it and search and replace the project key, this is the simplest I can do for…

Hi @LAL How come there is no repo, as you have made tests, test sets and test plans, they are in the test repo from Xray by default. I would urge you to go over the Xray documentation Why don't you create different test executions for the same test? You can assign a test execution to different users or via a Test Plan and…

Hi @Rob Lynam-Wilkes If you are not a Jira Admin, you are not able to do this. You would need to ask a Jira admin to create you this custom field and the context. See als this link for documentation. https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-custom-fields/

Hi David You can set up your customer permission to give your customers the ability to create issues without logging in, go to Project settings -> Customer permissions and set them as below : Then click on change the Global settings and allow anonymous creation like so : This will allow your customers to create issues…

Hi @[deleted] Or have one of the accounts stripped of the license and disable the accounts, instead of revoking. This needs to be done within Atlassian Access as well See: * update-roles-and-properties-for-jira-users * remove-or-suspend-a-user 

Hi @Rob Lynam-Wilkes I would suggest to create a Custom Field (Singe or Multi select) in Jira with the MoSCoW values. Put this field on the screens used in the Product Team. If the same screens are used within the whole company, set the Custom Field Context to only the product team project or projects. You can JQL that…

Hi @Fitzpatrick, Oliver You might could re-index the project. Or is there something wrong with the filter of the board you are trying to copy, or the sub-filter. Is this board shard with another project, that might be archived.

Hi @Abby O_Connell Atlassian has documented how to import information via CSV. This documentation can be found here I hope this will help you to import your required information

Hi @zacharoula_brinia So that means that the status (workflow status) of the issue is related to the column "Ready To Deploy" in the 1st board, should also be placed under the column "Ready by QA" in the second board A board is a visual representation of a team’s workflow within a project.

Hi @Misra Mohit Welcome to the community. Comala is not certified by Atlassian. It is an app on the Atlassian Marketplace. Marketplace apps do need to follow Atlassian guidelines/requirements, but there are no certifications for apps. On the Atlassian Marketplace there are more apps that can provide page approval options.…

Hi @Anmol Fattepur , The structure for the JSON request can be found here, based on the required format. https://docs.getxray.app/display/XRAYCLOUD/Import+Execution+Results+-+REST+v2 So you need to use the Xray API to import test execution results. You need an Xray API key for the user who is executing the JSON call This…

Hi @Alejandra González Check the Internal Notifications on each project, probably roles are specified for notifications. Secondly check automation rules, that a per project, multiple projects or global

Hi @zacharoula_brinia Cloud you share details on the board you have created and how and what to view should be on the QA board.

Hi @Karl Edwin Eaves Might be a stupid question, but did you try to log off and on again and access the Manage Apps section again. Mostly helps me out.

Hi @sravani.x.battu Welcome to the community I would create separate rules for the action you are describing * Value Fix version changes * New issue requires Fix Version if under an Epic * Remove Fix Version

Hi @-Ibai Nicolás de Pedro There is currently no such option in Tempo. There is an open idea on the tempo idea portal you can follow for this topic. https://ideas.tempo.io/ideas/ETS-I-33

Hi @Владимир М. This is the only option you can do, "Reactivate" first and then you are able to downgrade to free. This can't be done on a suspended subscription. Or contact Atlassian via Atlassian Support to explain your current problem.

Hi @Elen Kuklina I would also use the option @Sayed Bares [ServiceRocket] suggested, but also change the trigger of your rule. Trigger: Issue Transitioned See rule below, I did used default issue types and status in this example

Hi @Perry Tancredi You can get all permission schemes in one API call. https://<your instance name>.atlassian.net/rest/api/3/permissionscheme/ If you want it per scheme https://<your instance name>.atlassian.net/rest/api/3/permissionscheme/{scheme id} example: https://<your instance…

Hi @Robin-Keith Green Welcome to the community Yes you can, but only if you have 3 agents licenses assigned. Jira Software is up to 10, but that is not the case for Jira Service Management