I cannot find an example from JMWE that is close to what I want to do. (I am not a programmer so I do a lot by example and error.)
I have bugs and features in one project and when someone hits a step in the workflow they have to decide if they want to copy the bug or feature to a different project. I want to use create issue once to clone the issue. The bug should be created/cloned as a bug and the feature should be created/cloned as a feature. The issue types are the same across the projects.
What would be the right syntax to detect a bug issue type and assign the new issue the bug issue type?
Hi Matt,
You can try and use the JQL filter(quick filter) like: duedate < now()
I hope it helps
Radosław of SoftwarePlant Team
but it will filter the issues.. whereas a user would want to see all the issues with the ones missing the end dates as bold/highlighted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alternatively, you can use the baselines to show the deadlines but you will be still required to spot the deviations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've also asked for this feature, I thought I remembered SoftwarePlant telling me it is in their backlog? But meanwhile, I use quickfilters. Not ideal, as it won't predict tasks in jeopardy of falling behind based on work logged compared to due date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Radosław (SoftwarePlant) Any news on this? It would really be a nice feature.
Maybe you could clarify if it is in the backlog?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.