We have one customer on GitHub, one on GitLab, and one on Gitea. All 3 of these work quite well for our size of dev teams (small). GitHub is out if you don't want a cloud, but the other two can be self-hosted. None of them separate issues from requirements from tests, but they all have numerous ways to tag and organize issues, which seems to work fine in practice. (I also don't understand why you'd want tests organized like issues... why not just create an issue for adding a test, write it and add it to the automated test suite, and then resolve the issue? If it's a documentation thing, then just use the wiki.)

As it happens, the largest customer is the one using GitLab and they are considering Jira now because GitLab is highly developer-focused and most of their employees are non-developers, and price for accounts is fairly high on enterprise GitLab, so they can't just give everyone an account. Meanwhile, the second largest customer is using the free version of Gitea and integrated it with Active Directory, so all employees automatically have an account if they need to interact with developers.

In reply to Re: (OT) Tracking Issues, Requirements, Tests by NERDVANA
in thread (OT) Tracking Issues, Requirements, Tests by afoken

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.