How to generate JWT TOKEN from Postman
Hi Doug & Team, There seems to be some confusion. Kindly help me out here as soon as possible. My issue is How to generate JWT token from Postman itself. I have SecretKey, access Key, AccoutnId, Zephyr base URL also. Please just guide me how to use these details to generate JWT token from Postman. I am not talking about usage of the JWT TOKEN. I am asking about the process of generating JWT token via Postman. Thank you
Your Journey to Atlassian Jira Cloud with Zephyr Squad
Greetings community, Surely by now, most of you are aware of Atlassian’s shift in strategy to become a cloud-first company. This has some important implications to anyone who uses their Server based products, including apps. TL;DR: Follow these steps to migrate your Zephyr Squad app data using JCMA: Follow Atlassian's guide to setup theJCMA Followour Cloud migration guide to complete the migration Key dates per Atlassian’s FAQ page: February 2, 2021 – Atlassian customers can no longer purchase or request a quote for new Server licenses. February 2, 2022 – you will no longer be able to upgrade or downgrade user tiers for your Server products or apps (with some exceptions) February 2, 2023 – Existing customers can no longer purchase Server apps on the Marketplace February 2, 2024 – Atlassian stops support for Server products and apps What does this mean for Zephyr Squad customers? From my calls with some of you, and what I keep hearing from our support team, is that many of you are already actively exploring your options. While some are choosing to stick with on-prem by moving to Data Center, many of you are making plans to migrate everything to Cloud, including apps. Here at SmartBear, we are committed to facilitating a smooth transition to Cloud for all our customers. This includes brining feature parity between Server and Cloud products, supporting automated migration tools like JCMA, and be compliant with a number of Atlassian Cloud security and reliability programs on the Marketplace. What is the recommended migration path to Cloud? Atlassian’s Jira Cloud Migration Assistant (JCMA) is your primary path to Cloud. It is an application that helps you move projects, users, and groups from Jira Core or Jira Software on Server to Cloud.The automated app migration functionality in JCMA is now in an open beta, which means that all users can migrate their app data over to Cloud. Are there any feature differences between Jira Server and Cloud versions of Zephyr Squad? If you want to move to the Cloud version of Zephyr Squad, it’s worth considering feature differences from Server. We’ve created a handy Server/DC vs Cloud comparison matrix where you can review these differences in detail. Are there any limitations regarding what data I can migrate using JCMA tool? Yes. Because of feature differences between the Server and Cloud versions of the Zephyr Squad, some data will not be migrated. Please refer to the ‘Known issues and limitations’ section of the Cloud Migration Guide. Are there any alternatives to using JCMA? Yes.Zephyr Migration Tool by SmartBear is another solution for migrating Zephyr Squad data from Jira Server to Jira Cloud. This approach is recommended if JCMA isn't working for you, and your Jira instance is middle-sized with a few projects, as this migration utility can migrate Zephyr Squad data only for one project at a time. What if I need any help with the migration? If you require technical assistance, please check out the Cloud Migration FAQ or raise a ticket with our support team. Tell us a bit about your Cloud migration journey I’ll conclude this post with a question to you, our awesome community. What is your plan of action around migrations? Please spend a moment to fill our this short survey to let us know!
Cypress - Zephyr integration | Gitlab CI pipeline
Hi, I have an automation suite which is hosted in Gitlab. I have schedules and they are running periodically. I wanted to have them in our test management system which is Zephyr Squad Cloud. In the documentation, I have seen that Junit format is supported and Cypress has capability to generate Junit report. But I am having problems with uploading some reports if they contain failure and if their name has some special chars like (underscore _, which is not listed under banned chars for JQL restrictions) I am wondering if any of you have such an integration. Here is the video: (124) Using Zephyr for Jira within CI/CD Pipelines - YouTube
Zephyr Squad REST API rate limits an how can I increese it
Hello, The Zephyr Squad REST API documentation says that the rate limits are: https://support.smartbear.com/zephyr-squad-cloud/docs/api/index.html Rate limits 1,000 requests per hour. 24,000 requests per day. but my doubt is if that limits are for account/user or organization, and how can i increese that limits.`status` param ignored when creating execution via API
We're adding integration to Zephyr Squad via API. According to the documentation for the `create_execution` endpoint, we should be able to pass the parameter `status`, as an Object and set it to whatever value we want. We wanted to have this attribute set to "WIP". However, this parameter is simply ignored. These are the bodies of the request that were tested: '{"status":{"id":3},"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' # supposed to be the right one '{"status":{"name":"WIP"},"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' '{"status":{"name":"WIP","id":3},"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' '{"status":3,"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' '{"status":{"id":1},"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' Neither of the above worked and each time in response we were getting an execution with the status "UNEXECUTED": ... "status":{"name":"UNEXECUTED","id":-1... Is there something we can do to make it work? Temporarily we'll be using a second call to update the created execution on the `update_execution` endpoint.
Zephyr Jira Cloud API - Update execution
Hi, I'm trying to update the status and/or comment of a test execution. As recommended through apiary (https://zephyrsquad.docs.apiary.io/#reference/execution/update-execution/update-execution?console=1), I'm doing this through curl, with raw json (--data-binary argument): curl -s -S -k --include --request PUT -H "Content-Type: application/json" -H "Authorization: JWT ${jwt}" -H "zapiAccessKey: ${ZAPI_ACCESS_KEY}" --data-binary "${data}" https://prod-api.zephyr4jiracloud.com/connect/public/rest/api/1.0/execution/${execution_id}--write-out "%{http_code}" 2>&1) With "data" being the json request body (sensitive values redacted) = {"status":{"id":3},"id":"[EXECUTION_ID]","projectId":[PROJECT_ID],"issueId":[ISSUE_ID],"cycleId":"[CYCLE_ID]","versionId":[VERSION_ID],"comment":"Test Comment"} And I'm receiving the following error: HTTP/2 500 date: Wed, 03 Nov 2021 14:14:13 GMT content-type: application/json;charset=utf-8 content-length: 134 server: Apache-Coyote/1.1 {"errorType":"ERROR","clientMessage":"We encountered some problems during processing this request. Please try again!","errorCode":104}500 I'm also getting this same error when running it in the Production console on apiary. Up until this point, I've had no issues with GET (for execution lists, cycles, folders, etc.) or POST (creating new folders or tests) requests. Also, the JWT generation and usage has been working fine. If that were the case, I'd expect the "Expecting claim 'qsh' to have value x but instead has the value y" error. So this error is new to me. I've tried every permutation imaginable, I believe I've captured all documented required arguments. Does anything stick out as obviously wrong? The solution for the "Zephyr Cloud API - automated creation of execution" topic had me concerned that it might be a similar documentation error - "From the documentation the cycleId is optional in the cloud API, however in the server API the cycleId is mandatory" https://community.smartbear.com/t5/Zephyr-Squad-Questions/Zephyr-Cloud-API-automated-creation-of-execution/m-p/211313 While that topic was referring to creating a new execution using a POST request, it is the same API url and error message. So I wonder if something similar is happening here. Any help would be greatly appreciated, thank you! Greg
