Again a very well explained and helpful video. Thank you very much. In addition to the video, I have a few comments that users should be aware of and a few more that I have noticed as potential for improvement, with a request to TestRail to include them as a feature request on my behalf: 2:35 & 7:20 & 8:01 Unfortunately there is no way for Jira users without a full priced TestRail account to view the information at all. There should be the possibility in TestRail to create as many guest accounts with read only permissions without having to pay extra. 6:41 It would be helpful and more readable if the ticket preview in TestRail kept the rich text formatting from Jira instead of replacing it with markdown formatting. 9:46 The chart design could use a facelift and be modernized. In my opinion, the chart looks like it was created with a program from the last millennium. 10:04 It is very good that I can find out in TestRail which Jira reference does not yet have a test case, but what if you have forgotten to link a complete Jira Epic as a reference at the milestone? (E.g. because it was created after the milestone was created by a user without a TestRail account) Then of course it does not show up in the TestRail report. How can I do the cross-check in Jira and find out which Epic does not yet have a TestRail reference?
@testrail
Жыл бұрын
Hello, Thank you so much for your detailed feedback! We have an open feature request for #1, so we would be happy to add your vote. We have forwarded the feedback to the concerned teams for #2, #3, and #4. Also, please feel free to submit a feature request for any additional feedback you have: support.gurock.com/hc/en-us/requests/new?ticket_form_id=7738788856596.
@BettSwinger
Ай бұрын
@@testrail There is another important and huge problem: When creating milestones and TestRuns and TestPlans, we often cannot link all Jira tickets because the maximum length of the “References” input field is limited to 250 characters and is far too short. For tickets in the format “ABCD-####,” only 25 tickets can be linked. Instead of entering the references in a text field, it should be possible to add any number of reference objects. In addition, the import process is very time-consuming and should be simplified. The current workflow is as follows: Jira export of the issue list in CSV format, where all ticket numbers are one line. Convert CSV so that all ticket numbers are in one line, copy ticket numbers from the CSV to TestRail and hope that the list can be copied completely into the text field and is not cut off after 250 characters. Yes, I have already contacted the support team and received the following response: > TestRail doesn't currently support more than 250 characters on a string field which the "References" fields are. > But we have already submitted an internal request to explore improving/increasing this in a future product update to our internal team for evaluation. > > We can't provide any specific timeline for when that improvement will be available or if it will ever be available. > For now, we've added your feedback and your account to the internal ticket request to help the development team to prioritize the ticket. > If ever this feature gets released, you can check our release notes from the link below: So you are telling me that TestRail does not scale sufficiently to meet the requirements of large enterprise projects. And you can't even give me a time horizon as to whether this is on the roadmap in the near future or will be implemented at all? And it seems that fixing it is not a high priority for you either. I would have expected better from a professional test management solution that has been around for almost 15 years. Very disappointing indeed.
@manikyabandaru1554
4 ай бұрын
HI -Thank you - Can you please let me know if the test cases in JIRA can be mapped to test rail ?
Пікірлер: 4