Skip to end of banner
Go to start of banner

Troubleshooting

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 4 Current »

Each Jira task contains:

  • Proper title describing what? and where ([Manager] / [SDK] / [Prebid] / [GAM sync] / ...)

  • A description of what should be done

  • A design of how it should look (if needed)

  • Assigned priority (highest = should be fixed asap / medium = can be fixed during current sprint / low = can be added to the backlog)

  • Related issues or blockers

  • Has pre-planned sub-tasks

Each Jira bug contains:

  • Proper title describing what? and where ([Manager] / [SDK] / [Prebid] / [GAM sync] / ...)

  • Description of actual behavior:

    • screen recording to show the issue

    • screenshots (of entire browser, not just a console)

    • (optional) logs generated using atf_debug parameter (SDK debugger) steps to reproduce the problem

    • Sending a Alert via the Alert Tool

    • URLs to reproduce the problem

    • More useful information:

      • which websites (one publisher / many publishers?)

      • mobile /desktop

      • browser & system

      • the frequency of the issue, does it happen all the time or just at some points of time

    • Description of Expected behavior

    • Priority (urgent = should be fixed asap / major = can be fixed during current sprint / minor = can be added to the backlog)

    • Contact person

    • Related issues

  • No labels