• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      sclowes and team are implementing BTF analytics in the growth-plugin that ships with JIRA, Conf et al.

      They will be using a common set of code across all prodcuts and need us to remove our "opt-in" analytics from JIRA that we implemented in 6.1

      More info on how it was implemented:
      https://extranet.atlassian.com/display/JIRADEV/JIRA+BTF+Analytics+Spec

            [JRASERVER-37153] Remove "opt-in" analytics messages from JIRA

            Adding links to relevant issues.

            Marty Henderson (Inactive) added a comment - Adding links to relevant issues.

            NickN added a comment -

            ohernandez, this is for BTF, but not a blocker for 6.2 - so long as it goes in 6.2.1. Cool?
            //cc shoughton.

            NickN added a comment - ohernandez , this is for BTF, but not a blocker for 6.2 - so long as it goes in 6.2.1. Cool? //cc shoughton .

            nstrybosch This was worked on by jderaedt / jhazelwood? As per HC convo, we need to find out whether this really blocks 6.2

            According to a chat I have had with jderaedt, GreenHopper already depend on the system property set by JIRA and there might some other plugins doing so. IMO, with thee information I have so far, this looks risky this late into the 6.2 cycle and jderaedt is on DoS right now? So I would prefer this be done for 6.3 / 6.3 OD-1

            What do you say jdevenny?

            CC: mtokar

            Oswaldo Hernandez (Inactive) added a comment - nstrybosch This was worked on by jderaedt / jhazelwood ? As per HC convo, we need to find out whether this really blocks 6.2 According to a chat I have had with jderaedt , GreenHopper already depend on the system property set by JIRA and there might some other plugins doing so. IMO, with thee information I have so far, this looks risky this late into the 6.2 cycle and jderaedt is on DoS right now? So I would prefer this be done for 6.3 / 6.3 OD-1 What do you say jdevenny ? CC: mtokar

            NickN added a comment -

            Yes, needed BTF. I'm guessing these didn't hit triage because they're not bugs. ohernandez which team is best placed to tackle these?

            NickN added a comment - Yes, needed BTF. I'm guessing these didn't hit triage because they're not bugs. ohernandez which team is best placed to tackle these?

            Aren't these needed for BTF? nstrybosch?

            Simone Houghton added a comment - Aren't these needed for BTF? nstrybosch ?

            They don't need to be done in 6.2 (it would be nice though). If they aren't, they'll need to be done first thing for 6.3-OD1 (that is a MUST).

            nstrybosch is all over this one I believe.

            Josh Devenny added a comment - They don't need to be done in 6.2 (it would be nice though). If they aren't, they'll need to be done first thing for 6.3-OD1 (that is a MUST). nstrybosch is all over this one I believe.

            nmenere jdevenny - these stories are meant to be included for 6.2.
            Are you resourcing these asap?

            Simone Houghton added a comment - nmenere jdevenny - these stories are meant to be included for 6.2. Are you resourcing these asap?

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              shoughton Simone Houghton
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: