Tarun Sapra Community Champion

Hello @Sinclair Once the JIra issue is delete, it's completely gone and there is no way apart from the above mentioned link that I know of to retrieve the lost issue.

Hello @Angel Alvarez Could you reiterate your requirements and share the snapshot of your JQL along with the version of Jira which you are using.

Hello @Angel Alvarez You can create a JQL filter based on the query assignee = currentUser() and labels is empty In the boave query you can use your username as well instead of "currentUser()". This query will fetch issues assigned to you and without labels. You can save this filter and then on the dashboard use the…

You would have to use "RemoteLinkManager" instead, as Jira issue is connected to confluence via remote links and not via normal issue links import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.link.RemoteIssueLinkManager import org.apache.log4j.Level import org.apache.log4j.Logger Logger…

Ofcourse this is not a sustainable solution but atleast we would get to know that the issue is related to indexing.

That's strange, once the clone issue is created and the custom field value is visible on the view screen of the issue, could you please "re-index" the project. The option to reindex project is present in the project admin panel section. Once the reindexing is done then could you check again if the custom field value is…

Hello @PJ Wysota Indeed, not used to queries around IQL in the community, just comes across too much similar to JQL :) I have upvoted your answer!

Hello @Jamil Rahimov It's pretty easy to execute JQL via groovy/ script runner. You have to use SearchService and QueryParser Please see here https://community.atlassian.com/t5/Marketplace-Apps-questions/How-to-run-JQL-query-inside-Groovy-script/qaq-p/194691

Hello @aleksander_lebiedowicz Could you give it a try, post-functions which are using issue objects generally should be at the end of the list.

Thanks @Rik de Valk _Brainboss_ for creating this ticket, I have voted for this feature.

Hello @Rik de Valk _Brainboss_ I think this feature has to do with this ticket -https://jira.atlassian.com/browse/JPOSERVER-1663 But I don't see an open ticket especially for the requested feature, may be you can create an new ticket.

You can always have a custom field which can be single or multi select having the list of values which are basically assets and when you create an incident or bug then you can map them to the corresponding asset. 

Hello @Jonnada Kiran What do you mean by "associated to a particular screen", could you please elaborate a bit more.

Hello @aleksander_lebiedowicz Could you move the post-funciton * ScriptRunner workflow function - Clones an issue, and links (condition & additional actions apply). Issue will be cloned to project same as parent, with issue type Concept To the last position i.e. after the "Fire a Generic Event..."

https://community.atlassian.com/t5/Answers-Developer-Questions/Count-number-of-Resolved-Subtasks/qaq-p/515373

Similar questions here https://community.atlassian.com/t5/Jira-questions/Count-the-number-of-subtasks-on-an-issue/qaq-p/353542 https://community.atlassian.com/t5/Jira-questions/sub-task-count-of-a-parent-issue/qaq-p/335292…

Hello @Stephen Gendreau This is doable but not out of box, you can create a scripted field and map it to the story type. The scripted field can show the value based on the sub-tasks resolved under the parent issue. For scripted field you would require script runner plugin which offer quite a lot of features. It's a paid…

Hello @Eoin O'Neill Could you please share some screenshots.

Sure, @Andrew Cross. If it works for you and you are happy with the answer. Please accept/upvote so that other are helped as well. Thanks.

You have selected your swimlanes as story thus you aren't able to drag your stories on board, so you can try to disable the swimlanes based on stories in the board configuration. You can also open the story in view screen in a separate tab and move it to the status like "UAT passed" or any status that has transition to the…

"Move to deployed" , here deployed is the name of the right most column that's why it says move to deployed and that generally happens when all the sub-tasks of the stories are closed and only story is left open. I think I know the reason why it's happening The story which is dev-done has a transition to "prod-deployed"…

Hi @Andrew Cross This is happening because it seems some of the sub-tasks might be in status not present in the column mapping. For stories where you don't see the button "move to deployed" then there would be some sub-tasks which are not moved to the "right most" column of the board. If you open story in issue view screen…

Hello @Sandra Kawamoto Per Story if you want to see progress percentage then it is something which you might not find out of the box. If you are using porfolio then you can track progress in percentage https://confluence.atlassian.com/jiraportfolioserver/status-and-progress-tracking-715263088.html Though portfolio doesn't…

Your JQL filter should include the stories and statuses of the stories should be mapped to all columns of the board. If any status is not mapped then the story in that status will not appear on the board.

Put the above condition in the "condition" section of workflow script runner and that should do the trick. Now the workflow button for close will not be visible if issue has less than 2 labels. But I have a feeling that you should put in the "validation" phase instead of condition phase that's much better.

Please see samples here - https://scriptrunner.adaptavist.com/5.0.2/jira/recipes/workflow/conditions/all-subtasks-resolved.html passesCondition = true def labels = issue.getLabels() if(labels && labels.size() < 2) { passesCondition = false }

Hello @Andrew Cross Since you have mentioned " the Subtasks can remain, but I dont need to look at them on the board" Thus, have you tried removing sub-tasks from the underlying JQL filter of the board. Basically having in JQL "type not in sub-task " Something like this, so that the board doesn't fetch sub-tasks at all.…

Purpose of Jira is to track projects and currently there is no way to "version" individual tickets. You can use "fixVersions" across group of tickets and then release them via the project admin panel. But individual tickets are made up of fields and fields are editable and thus you can' version the content of the fields…

Currently it's not possible to have the themes which you can create in portfolio to appear in Jira as a custom field on the issue create screen thereby giving the user an ability to assign an issue to theme via the Jira interface instead of portfolio. https://jira.atlassian.com/browse/JPOSERVER-525…

When do you want to copy the reporter i.e. when do you want to want to trigger this operation.