Jump to content

Search In
  • More options...
Find results that contain...
Find results in...

JIRA workflow?

Warning: Please note

This thread was started before GSAP 3 was released. Some information, especially the syntax, may be out of date for GSAP 3. Please see the GSAP 3 migration guide and release notes for more information about how to update the code to GSAP 3's syntax. 

Recommended Posts

Hey! Are any of you guys using something like JIRA or Asana in your organizations to track your banners? Any recommendations or outlines for workflows or best-practices?

Link to post
Share on other sites
  • 3 weeks later...

One jira ticket per banner.  The ticket must include RM platform, PSD path and expected name convention.  We receive the ticket from the PM then send to Art Director for approval and then QA.

  • Like 1
Link to post
Share on other sites

That makes sense - thanks! Do you guys use the same workflow for bigger campaigns? We sometimes have buys that are like 64 units and more (many, many more... ?).

Link to post
Share on other sites

We have done it for a 200+ campaigns.  The PM will complaint about the amount tickets (they are responsible for creating them) but from my perspective is the healthier approach for a seamless DEV & QA communication since sometime the feedback is per ad unit.

  • Like 1
Link to post
Share on other sites

Gotcha - yeah, I was wondering about that. Cool, well it's helpful to know that's how some people manage their campaigns. Thanks!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.