Using the Jira Release plugin in combination of BitBucket, there is the option in the report to display warnings for tickets not following the workflow, such as "Unreviewed code". In our case, we had a ticket and we committed some code into a feature branch for that ticket except during development of the ticket, we decided to kill off that feature and drop it. So we deleted the branch(including on BitBucket) and close the Jira ticket as "Won't Do"(GIT still has history of the commits). Except now the ticket shows up in the Unreviewed Code because there are dead end commits against the ticket and the ticket is "closed".Is there a way to configure the warnings to not check tickets which are specific statuses, such as "Won't Do", etc?I suppose we could try to rebase our GIT history or prune the "unwanted" commit and hope the Jira ticket will no longer have the commits. Then if that doesn't work, we'd have to create a fake pull request to a to-be-deleted branch to merge it into to satisfy the warnings.To reproduce this:1. Create a Jira ticket and add it to your board2. Create feature branch for the ticket3. Commit / Push code to remote against that ticket in a feature branch4. Delete the branch on remote server (BitBucket)5. Close the ticket as "Won't Do"6. The warning will now be listed in the release reports

Community
Q&A
Jira
Questions
Jira Release Report shows Abandoned ticket/code as Unreviewed Code

Jira sub tasks issue - giving error

After migrating the data from Jira cloud to Jira server, we have observed that for issuetype = 'subtask', the description field is giving below error message.

Kindly provide me your valuable suggestions

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.web.component.subtask.SubTaskSequenceColumnLayoutItem threw exception java.lang.NullPointerException: null value in entry: actualSequence=null at templates/jira/issue/table/macros.vm[line 117, column 34] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:342) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:507) at

1 answer

1 accepted

1 vote

Answer accepted

If you remove the ticket from the release by clearing the fixVersion field, the error should go away.

There's not much value in listing what didnt make it into a release anyways.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Talk about over complicating it, thank you for the simple solution.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Jira sub tasks issue - giving error

1 answer

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events