What does it mean in the product settings in the administration panel "New users have access to this product", new users will not be able to choose a Jira product, if, for example, they were initially invited only to confluence?
How would you know if sub task exists or not?
You have to make assumptions based on your business logic.
For example (and this is a real one I wrote listeners for, although I've simplified)
If the issue is edited, the attendees field has Laura added. So, my code has to go:
In this case, the logic is quite simple, and the users know that if they edit a summary of a sub-task, they may end up with a duplicate. We're not yet enforcing a stronger check in code, just monitoring it to see if it does become a problem.
I think @SidhR needs to look at his business logic, and work out how to answer the question "does this sub-task already exist" in that context.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the clarification Nic. This is what I have managed so far but still having hard time what to compare the Summary with?
def reqAssignee = 'xxx'
def swAssignee = 'xxx.'
def testAssignee = 'xxx'
Collection allsubtasks = issue.getSubTaskObjects()
for(Issue allsubtask: allsubtasks) {
def subtaskSummary = allsubtask.getSummary()
log.info("Subtask Summary" + subtaskSummary)
if (subtaskSummary == (compare with ?){
log.info("Subtask already exists")}
else {
m119VersionArray.each{ version ->
createSubTask("", version, "_Approved_REQ", reqAssignee)
createSubTask("", version, "_Approved_SW", swAssignee)
createSubTask("", version, "_Approved_TEST", testAssignee) }
}
}d
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.