Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-5921

Labeling files

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      According to customer's description:
      "I'd like to be able to label all files in my project as either "compliant" or "non compliant". It's a little bit like the "Favorite" label, but I'd like the label to be shared by all users, and I'd like to see it when I look at the list of all files in Source."

      The use case:
      "We are working on code that will be part of an FDA submission. All the
      code needs to comply with our Software Development Plan. Since we have
      a lot of legacy code, we are bringing it into compliance. Some of the
      files are compliant, some are not, and some are somewhere inbetween.

      Non-compliant can mean several things. For example, the file hasn't
      been reviewed or the appropriate level of testing hasn't been
      provided."

            [CRUC-5921] Labeling files

            Marek Parfianowicz added a comment -
            Atlassian Update – 5 October 2018

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Regards
            Marek Parfianowicz
            Fisheye/Crucible TL

            Marek Parfianowicz added a comment - Atlassian Update – 5 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL

              Unassigned Unassigned
              cayres@atlassian.com Camila Ayres [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: