ContributionsMost RecentMost LikesSolutionsTraceability report export workarounds? Hi Community, Does anyone have a workaround to get traceability reports into excel? The two ways I have tried so far is literally copy and pasting from the visual report in to excel - no surprises that that didn't go well 🙂 Then I tried saving as a PDF and using Acrobat Pro to export to excel - that was marginally better but the table formatting requires a fair of rework and you get all the icons and graphics embedded too, so it's not something that could be integrated into an automated reporting workflow. I would welcome any ideas around this. I can see traceability information is contained in the execution excel exports so I assume this is the only way to do it via exporting currently? Not the end of the world but I'm trying to avoid as much excel jiggery pokery as possible. (side note: I've also raised a product feature request for the ability to do traceability reporting on the linking done at a test cycle level. I can't even fathom the point of being able to link test cycles to jira issues if you can't then report on it!). Why does the roadmap hardly change? Hi folks, For most of 2023 the Zephyr Cloud roadmap has remained static. Well, certainly the 'planned' and 'in progress' categories has remained the same for ages, with the only items in them being 'data residency'. Can anyone from Smartbear confirm or deny if this roadmap is an accurate reflection of what the actual dev team are working on? (I'm not asking for the details, just some sort of indication that there are actually more improvements in the internal pipeline, planned). The reason I ask is that certainly the impression this gives is that the product is going to remain static for a long time and that none of the many good, and useful, ideas 'under consideration' are going to materialise any time soon. I think this erodes confidence in the long-term viability of the tool. I'd love to see some of those ideas move forward 🙂 Many thanks. Permissions for viewing test executions Hi, I have a question about limiting access to test execution information. Background: We are running a Jira cloud instance that supports our work with multiple (20+) externals organisations. For data security reasons each organisation has their own Jira project so that they cannot access the issues and data of the other organisations (issue level security was not a feasible solution to manage this, with so many different groups of users). All organisations must execute the same tests, so we have set up a 'central' Jira project purely for hosting all our test cases in Zephyr. So whenever a new product release is made we make sure our tests are up to date and then in each organisation project we create a new test cycle and then add the tests from the central project. This reduces effort because if we ever change a test case in the central project, this change can be propagated easily to all the organisation projects that are pointing to that test case (as opposed to importing/exporting, or manually changing, the test cases in each project!). Observations: We need to enable the 'browse project' Jira permission on the central project to allow the organisation-level users to be able to actually see the tests when they come to execute a test cycle. But that's ok as we have made sure the zephyr permissions in the central project mean that those test cases can't be altered by them. However, acting as an organisation user I have noticed that if I click to view the test case, I can then go to the 'executions' tab and see the entire execution history for ALL projects that use that test case, even if I'm not a member of those other projects. Now granted I cannot actually click on the execution key and view all of the sordid details in it, but even on the execution tab for a test it shows usernames, issue counts, status etc. which is all information that we'd like to prevent user of other organisations seeing. Question: So is there a way to prevent users seeing the execution history of a shared test based on the project they belong to? Zephyr Scale (Jira Cloud) import Hi all, In the Zephyr Scale Data Center vs Cloud feature comparison here: https://support.smartbear.com/zephyr-scale-server/docs/features.html In the 'Importing Test Cases' section it says that you cannot import test cases from other Jira projects, but that you can from Zephyr Scale. I need to understand what 'other Jira projects' rules out. What I'm intending to do is have multiple projects in the same Jira Cloud instance, all with Zephyr Scale available. I need to be able to import tests from one project to another, using the Zephyr Scale import wizard. So, is this going to be possible?