4 ms·

I find the problem is that engineering wants one work flow, product wants another, another department wants theirs, and so on. As a CTO I have declared that Ji

• ivan_gammel 4mo ago
  Sounds… political. You have cross-functional teams interfacing via a tool. It would be reasonable to co-design this interface, so that all user goals are taken into account. When engineering owns the tool, do they approach the configuration of JIRA the same way as they build the product?
  • l72 4mo ago
    We approach tickets that match with our development strategy. A ticket is tied to and represents a branch of code. When that code is merged the ticket is done. It cannot be reopened, you open a new ticket and link it and there will be a new branch. I know everything that is in our main branch by looking at jira. Product mangers and executives often want a very different view or workflow and it is hard to bend jira to work for everyone. Jira would need to have things like parallel workflows on a ticket and that would just get confusing and complicated.
    • ivan_gammel 4mo ago
      > it is hard to bend jira to work for everyone it is not, as long as focus is on goals rather than on solutions (applies to everything). Nobody needs a view or a workflow. Everybody has jobs to be done. That is the starting point in process design.