Contributions
- 3Views0likes0Comments
Atlassian Team24
Not sure if this is the right forum for this. I will be attending the Atlassian Team 24 conference in Las Vegas April 30-May 2, 2024. This is my first time there, so I am not sure exactly what to expect. I am hoping to have the opportunity to meet others that use Zephyr Scale. I am hoping to be able to talk, show, discuss and banter about what has worked (or not worked) for others with Zephyr Scale. This community forum helps and is good, but is much different than having a conversation. Let me know if you are going, i would like to meet up and talk.10Views1like2CommentsRe: JQL Search for Estimated Time is NULL / BLANK
I was able to talk to a coworker and he helped figure this out. Wanted to let other's know the solution. I found out that you can find estimated time ranges within the query. project = MGS and issue in coveredByTestCasesHavingField("estimatedTime", "00:00" , "00:05") project = MGS and issue in coveredByTestCasesHavingField("estimatedTime", "00:05" , "99:59") Query 1 will give estimated times <= 5 minutes, and Query 2 will give estimated times >= 5 minutes. Armed with this knowledge, we realized we can find empty estimated times by finding anything outside the 0 to 99 hour range. project = MGS and issue NOT IN coveredByTestCasesHavingField("estimatedTime", "00:00" , "99:59") This method requires that a test case is linked to an issue. There may be another way to do this, I am interested to hear if there are other solutions, or better yet if there is a way to do this within Zephyr without needing to be linked to an issue.13Views1like0CommentsJQL Search for Estimated Time is NULL / BLANK
Is there a way to do a query/filter on estimatedTime that has not yet been entered? I was able to find this information: https://support.smartbear.com/zephyr-scale-server/docs/en/jql-functions.html#UUID-bb04c337-22d6-fee6-7703-b4515a68234c_N1697097036420 I saw this example in the documentation and it seems to work as expected, but is limited to only filter an exact value: project = MGS and issue in coveredByTestCasesHavingField("estimatedTime", "03:00") I would like to use this to find all issues with test cases where the estimatedTime has not yet been entered. I tried using synatax of ("estimatedTime", NULL) and ("estimatedTime", BLANK) and these did not work. I also used ("estimatedTime", 00:00) but this is not the same as it not being entered. As a follow-on related question: is there a way to use this to search for estimatedTime > 00:05 or < 00:05 as an example?Solved13Views0likes1CommentRe: Burn Down Charts
Butch, I am still working with them on this. They have requestied a lot of our data, which is hard for me to provide. We are on data-center due to our security requirements and getting them full sets of project data they requested is not easy. This issue seems pretty obivous to me, and I even mentioned in my communications to them about you having the same issue. Are you on cloud? They may be able to see your data easier if you open a similar ticket. In digging into this, I have found that there may be a couple of (non-ideal) workarounds available. When you generate a report, you can export all that data into excel. From there you could potenially manipulate the data into a semi-useable form. In Jira, there is a way to create your own dashboard gadget, and there are zephyr dashboard gadgets that match the zephyr reports. I am ASSUMING that there would be a way to create your own gadget that would create correct burn-down charts. Both of these would require extra-ordinary effort to do, and something that I would expect SmartBear to provide out-of-the-box.15Views1like0CommentsRe: Burn Down Charts
Andy, I appreciate the followup. At least there is some positive news and potential updates in process! From the feedback you got, it sound like SmartBear thinks they are displaying (correct) information in a (wrong) manner. I believe that in my case they are displaying (wrong) information in a (wrong) manner. I have been back and forth with SmarBear on my issue. They cannot reproduce what I am seeing (yet).35Views1like0CommentsDetermine Amount of Effort (time) Remaining
I think this relates to a quesion that Butch had in this discussion: https://community.smartbear.com/discussions/zephyrscale/how-to-view-estimated-time-effort-in-reports/262576 Is there a way to determine how much effort there is remaining for a test cycle/plan? At the start of a cycle, you can look at estimated time, and know where you are at. If you are executing the cycle there are reports to see how many cases are at each staus (pass/fail/not-execucted). However, I would like to see how much time/effort is remaining based on the estimate. example: There is a cycle with 100 test cases. The total estimate is 100 hours for simple math. However, half the cases take 1.5 hours, and the other half take .5 hours. The engineer responsible for estimating is not always accurate. The test cycle now has half the cases excecuted, and there are 50 hours used. Is it going to be complete early, late, or on-time? That would depend on which test cases had been executed. It also could be that all the 'quick' ones were done first, but were misestimated and it is going to be REALLY late, or all the long ones were done first and it is going to be done REALLY early. alternate example: I have 4 test cycles with varying numbers of test cases in them. We have decided to SKIP (state that we use) 70% of the test cases in 2 of the cycles, as these tests were decided to be not required to validate the software on this hardware change. How can I recalculate the estimated time for these cycles? In this situation, there are 30 test cases that take a total of 6 hours, however one case takes 3 hours to run. Do we really need to look at 30 individual test cases and add them up manually (or not) to see how long this is going to take?19Views0likes2Comments