Duplicate project

[David Spire]

Hi there,

We are now facing an issue which is that too many themes of our platform is managed inside 1 discovery project, with too many list and too many people in there.

We were guessing if that would be possible to create a new discovery project on making a copy of parameters on an other one, as it is for other projects in Jira.

Best,

David

[Pieter Helsen]

Just tried whether filtering the idea from the view based on its status would alter the score, but it doesn't (which, when I think about it, is expected, since one view should not show a different impact score compared to another).

With the 'done' ideas filtered out, I do feel that just picking the 'highest in the list' is probably still a viable way of choosing what to do next, but it would be nice to have the option at least to do what you propose. Functionally, you'd probably have the impact score for completed ideas set to '--' or something similar in the view and then recalculate the impact of the other ideas accordingly. 

For your reference; we have an 'impact calculation' view which we use to assess the values that make up the impact score and then use to plan our next release (just picking the top ideas from several buckets). The view filters on 'Status' (no completed ideas) and groups on 'Bucket' (similarly to the JPD team's setup) where we have multiple buckets of work and we try to pick one or more from each bucket to make up the release. That way Non-Functionals don't get pushed to the bottom of the list for instance. 

[Nelson Tang]

Thanks Peter - this is an interesting workaround

[Jon Cutright]

I have been piloting JPD for a few months. I use 5 weighted criteria and because of the way JPD works with relative scoring and evaluating against literally every idea regardless of status, I am forced to use an absolute scoring model with a kludgy setup involving numeric fields and a custom formula to produce a score. Come on Atlassian, you can do better than this. I'm looking into other products that handle relative scoring more elegantly.

[Josh White]

Agree - without this, over time, the scoring will become difficult to make sense of

[Anton Bildh]

Still not fixed by Atlassian...

[Andrian _]

Could you clarify if 'prioritization score' is a custom field you've created, if so sounds like the value is something you've assigned?

If so, it sounds like you'll need to set- up an automation for it, though it could be complicated because it's not just the 'next' idea you need to update, but all ideas not yet 'completed'.

[Nelson Tang]

The challenge with custom fields is that I'm using the 'weighted' method and not the formula. I still want the normalization approach but only on 'relevant' ideas (ie ideas that have yet to executed)