Anyone got a workflow for an "idea" issue type?

[JamieA]

I haven't done this since donkeys years and I'm a bit out of practice. Has anyone got a sample workflow for modelling an "idea"? Ie something that doesn't relate to bugs or code or operations, just someone might have a completely blue-sky "idea" like "can we have flowers on all the desks", "should we have a company masseuse" or something?

I imagine the idea would go through the create or germination step, then be tuned, discussed, and finally it would either be decided to implement it or not.

If you have something like this a picture from the workflow designer or JVIZ would be much appreciated...

[Beth Schaefermann · Accepted solution]

Just brainstorming here but...

transition: Create

STATE: OPEN

transition: Start Brainstorm (alternative language: Start Progress)

STATE: IN BRAINSTORM (Alternative language: In Progress)

transition: Flag for moderation

transition: Kick back to open

transition: Mark ready for closure

transition: Close

transition: Drop

STATE: REQUIRES MODERATION (Alternative language: Flagged for attention) <--Could also be a checkbox flag on ticket

transition: Brainstorm

transition: Kick back to open

transition: Close

transition: Drop

STATE: READY FOR CLOSURE <--Required if accountable person not present

transition: Brainstorm

transition: Kick back to open

transition: Close

transition: Drop

STATE: ON HOLD

transition: Brainstorm

transition: Kick back to open

transition: Flag for moderation

transition: Close

transition: Drop

STATE: DROPPED (alternative language: No longer relevant)

transition: Reopen

STATE: CLOSED

Resolution: Selected for implementation

Resolution: Rejected for implementation

Resolution: Duplicate

Transition: Reopen (moves to Open)

*I would have diagrammed it, but our instance is unavailable right now.

[Beth Schaefermann]

You might also check out how Jive handles ideas; it's the best I've seen: https://community.jivesoftware.com/community/features

[JamieA]

Thanks Beth that is also interesting. I'll check out Jive, I've also been looking at Kindling.

[Jo-Anne MacLeod]

How about a simple project on its own. One issue type: idea.

The create screen has nothing but summary and description.

Workflow is new -> Investigating -> feasible -> move to appropriate project

-> not feasible -> close

send out notifications as appropriate etc.

[JamieA]

Yeah, I like it... nice and simple.

[Norman Abramovitz]

Maybe what I did in workflow below would work for you. I added state before the open state called research. So the input transistion was create issue which went into research state. The output transistions was close and open. Anyone can comment on the issue that has create issues permission. You can then change the issue type to one of the other issue types if the idea is approved.

http://www.wix.com/nabramovitz/jiraworkflow1

You also can create a separate workflow with just these states and then copy the issue to another issue type if work will continue on it. There is a screen to assign issue types to a workflow. So workflow scheme would have two workflows.

[JamieA]

interesting, thanks.