Interraction between departments

[antonyneshore]

Example. I have development, design, marketing, qa, content deps.
I have some issuetypes (issuetype Task, issuetype Content, issuetype Bug, issuetype Marketing Task,issuetype Design).
The life cycle is:
PM creates 4 issuetypes (Task with all info, Content, Design and Marketing Task)
Dev team prepares code in Task, after that content team starts to their issuetype Content, after Content done, design team start to work. And only after all tasks are closed, the marketing department starts work.

How to prevent the case that the department will start work ahead of time?

[John Funk]

Hey Anonty,

We consider that all to be one process where a single ticket moves across a Kanban board into columns that represent each one of the activities you mention. That way we get a full lead time from start to finish for the type of work we are doing - emails, blogs, workbooks, landing pages, app features, etc. 

We have also implemented a pull system that helps communicate when the issue is ready to be work for the next activity. 

We do TONS of content across multiple teams and functions.  :-)

[antonyneshore]

Hi John, thanks for reply.

Each department works on their board.

Some of deps use kanban and other uses Agile boards with lots of other activities.

One board is not a good idea for me.

But tanks anyway for answer.

[Jack Brickey]

there are different approaches that I could think of but my vote for the best would depend on me better understanding your process. Off the top of my head I would suggest using automation addon to create the 'next' task for the other department once the current task reaches some status in the workflow. Another thought is that if your process is serial then maybe a single task that is 'passed' around?

[antonyneshore]

Hi Jack, thanks for reply.

1- addon - is good idea.

2- task passed around will not work in my case, cause I have diff issuetypes and my boss will not change whis flow

[Ravi Sagar _Sparxsys_]

Hi @antonyneshore 

Yeah you would need to use an add-on to either create a new task at the right time or check for the linked issues' status and only allow them to start the progress when their linked issues' are in a particular status. Using ScriptRunner you can add restrictions on the transition. 

Jira Misc Workflow Extension already has this condition in place.

Search on the community and you will find plenty of examples.

Ravi