How do you manage Jira status vs Feature status?


Badge

After linking with Jira…

Now we have Two statuses for every feature/Epic… the one coming from jira and the features status in PB.

What’s your flow on that? Also, does “filter by jira status column” shows duplicate status like ours?

 

Seems like a challenging exercise to define a consistent flow without lots of manual cleanup

 


This topic is closed for comments.

11 replies

Userlevel 7
Badge +13

@Jay great question. We like to think of the status in Productboard as being the steps/stages you move through from discovery to launch, while the status in JIRA represents just one small part of that -- the status of the work in delivery.

Tell me a bit more about how you’re thinking about this?

Badge

@scott.baldwin interesting thought! 

Usually the stages from idea to launch, eventually,  has 3 or 4 stages that are directly mapped 1-to-1 with Jira Status. And maybe 2 stages before and after jira. 
 

Before Jira: idea, discovery, backlog(ready whenever we want)
It’s in Jira: to do, in progress, done

after jira: announcement, released

 

the stages in jira, we try to update them manually.. for one reason: 

To have the roadmap views stay relevant and useful. 
 

To know what’s being worked on, what’s finished.. what’s coming up… by release, objectives or any other dimension.

 

This helps us, senior management and leadership having one stop shop on what’s going on. 
 

Currently we have lots of: “Oops, didn’t manually reflect that, check jira” or “hmm let’s check jira first to see how much we need to prepare”.


Noting that we use features and sub-features some times as “EPICS” and “STORIES”… so sometimes Jira roadmap view for epics is more updated/useful. 

Userlevel 6
Badge +12

What’s your flow on that? Also, does “filter by jira status column” shows duplicate status like ours?

We have the JIRA-specific statuses linked between Productboard and JIRA. There are a few PB-specific statuses that are more focused on delivery and conceptualization (we’re using a hybrid of Scrum and the Shape-Up Methodology, so the shaping and development processes are shared - while the reviews, delivery checklist, and conceptualization/design are all in PB).

Our “Filter by JIRA Status Columns” only shows one set of statuses. I’m curious, have you only mapped one project via the integration? If there are multiple JIRA projects syncing to PB, then shared statuses will display in this fashion (ala redundancy).

Userlevel 7
Badge +13

Thanks @Jay sounds like in your case then I’d have the following statuses:

In Productboard: Idea, Discovery, Backlog, In Progress, Announcement, Released
In JIRA: To Do, In Progress, and Done

Then I’d filter your roadmap views to include the status AND the JIRA status to get to what you need to see.

Badge +1

I’m piling in on this and have actually passed this feedback directly to our Productboard account manager - it’s beyond me why the Jira integration can sync status’ to a 3rd status field and not to the core feature status in Productboard :thinking:

Our goal is to make Productboard the source of truth for product development, but if the status’ in PB aren’t accurate, Jira becomes our source of truth - or as Productboard users we’ve got to spend time each week manually updating the feature status’ to match Jira status.

This seems like a no brainer.

Userlevel 6
Badge +12

I’m piling in on this and have actually passed this feedback directly to our Productboard account manager - it’s beyond me why the Jira integration can sync status’ to a 3rd status field and not to the core feature status in Productboard :thinking:

Our goal is to make Productboard the source of truth for product development, but if the status’ in PB aren’t accurate, Jira becomes our source of truth - or as Productboard users we’ve got to spend time each week manually updating the feature status’ to match Jira status.

This seems like a no brainer.

 

This seems to be one of those unique use-cases where there’s a stronger dependency on JIRA and less of a dependency on Productboard. What I mean by this is that Productboard would have more statuses than the feature’s existence in JIRA (as @scott.baldwin mentioned: idea, discovery, etc.).

It would likely cause additional concerns/conflicts if JIRA usurped whatever statuses that Productboard had a feature in (unless they were 100% 1-to-1 and you track ideation/conceptualization/implementation/documentation/deployment in both Productboard and JIRA). I think this is an edge case that will require additional vetting through the community, mostly to weed out additional edge cases like this one.

Badge

I’m piling in on this and have actually passed this feedback directly to our Productboard account manager - it’s beyond me why the Jira integration can sync status’ to a 3rd status field and not to the core feature status in Productboard :thinking:

Our goal is to make Productboard the source of truth for product development, but if the status’ in PB aren’t accurate, Jira becomes our source of truth - or as Productboard users we’ve got to spend time each week manually updating the feature status’ to match Jira status.

This seems like a no brainer.

 

This seems to be one of those unique use-cases where there’s a stronger dependency on JIRA and less of a dependency on Productboard. What I mean by this is that Productboard would have more statuses than the feature’s existence in JIRA (as @scott.baldwin mentioned: idea, discovery, etc.).

It would likely cause additional concerns/conflicts if JIRA usurped whatever statuses that Productboard had a feature in (unless they were 100% 1-to-1 and you track ideation/conceptualization/implementation/documentation/deployment in both Productboard and JIRA). I think this is an edge case that will require additional vetting through the community, mostly to weed out additional edge cases like this one.

Id be happy to jump on this as well as we are also trying to truly understand the benefits of the Jira integration if we need to still go into Jira for the source of truth of where we are at with the feature releases 

Userlevel 7
Badge +13

@Jmodiz love a good pile on 😀but for reference, the JIRA integration can still help you see where you’re at with releases and displays a status per feature directly from JIRA -- no gaps there. We just don’t sync JIRA status to Productboard status and treat them as separate entities today. Check out our help center articles about the JIRA integration to learn more.

Badge

@scott.baldwin is this by design or will there be a future release that enables integrating that too.  Thanks in advance for the answer :) 

Userlevel 7
Badge +13

@Jmodiz it’s by design right now for the reasons mentioned above -- your Productboard status may be different than the JIRA status. Our team continues to collect feedback and may make changes here in the future. Feel free to leave your thoughts here: https://portal.productboard.com/pb/1-productboard-portal/c/187-enhance-jira-integration

Userlevel 7
Badge +13

@jameshanley and @Jmodiz hopefully you’ve been enjoying the improvements with the ability to sync JIRA status and Productboard status is it helping you out?