Comments
-
I recommend to use Power Scripts for Confluence , it allows you to create and configure webhooks which you can use to extend the confluence api functionality , I created a new webhook which which utilize there built-in function : removeUserFromContentPermission
-
@Bunty Most probably, you have a post function in your workflow on bug close transition. check and confirm you are not clearing the sprint field
-
@Kmmaughs You need to use update issue function import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.event.type.EventDispatchOption import org.apache.log4j.Logger def log = Logger.getLogger("com.onresolve.jira.groovy") def userManager = ComponentAccessor.getUserManager() def issueManager =…
-
I recommend to reach out the Atlassian support team
-
Unfortunately, this is not supported in JIRA Server /JIRA service desk
-
I recommend to install Prometheus+ Grafana Jira active monitoring 24/7 with Prometheus + Grafana this will give you a clear information by time and even notification for your threashold
-
it is their decision and I don't know the reason behind it. regarding your issue, I found this error that can be your problem, can you give a try to the solution. DataAccessException on Issues with Assignees that Have Been Deleted from Crowd
-
You can but not without 3rd party plugin like (Script-Runner) or developing yours. here are relevant questions Catching user login event? [SccriptRunner] - Custom listener in login - Userfailedauthentication envent
-
@NithyaSE No need to create any issue type you should use the created one by zephyr and from your picture it seems like installed successfully. check the created issue type and be sure it is linked to your project issue type scheme
-
Unfortunately, getCustomFieldObjectByName() is deprecated and getCustomFieldObject() is safe for your case
-
Seems like it is an existing bug https://jira.atlassian.com/browse/JRACLOUD-72311
-
as far i know this is not achieved without a 3rd party add-on. you can try script-runner (commercial) or MyGroovy (free) then you can add a custom script validator to verify all linked issues has component value assigned
-
@Andreas Gschwari I think your problem exist with the custom field configuration. as you need to specify the screen. please follow the instruction here carefully Configuring a custom field
-
did you used the right customFieldId. it should be like this def cfLastAssignee = customFieldManager.getCustomFieldObject(12003)
-
To Summarize The problem is that you need to update the resolution field for all closed issues if you have scriptrunner then it is easy task as there is a built-in function to update the resolution based on filter. if you don't have it you can update it by following the instruction here: HowTo: Bulk Edit Resolution Note :…
-
You can format your output value using the following method ${DateUtils.getDurationString($Value) ?: "0m"
-
Noel is right, Please note that the issue will hold more than one sprint in the sprint field if you moved not-completed issues to next sprint. which may have impact on your reporting if it is at your concern.
-
I meant You need to update the workflow by adding screen to “Set Resolution” translation And this screen hold the resolution field. This will make mandatory. you can mark the question as answered directly beside my first reply
-
I don’t think it is allowed for non-licensed users.
-
There is no mean to set it automatically to "Done" as not all your request will be resolved , some might be canceled/duplicate/declined.... etc. I recommend to make the resolution mandatory by adding the resolution field to the workflow screen when transition from "Set Resolution". the field will be mandatory.
-
@[deleted] I recommend to create issue filter then subscribe to it Please follow this instruction Subscribing to your search results and you will find detailed information about Constructing cron expressions for a filter subscription
-
Unfortunately, this is not support by JIRA. you can refer to the recorded feature and vote for it. also, you need to be sure to print the card on A4/A3/Letter page size as it fits will with these size
-
Please follow the instructions here to fix the problem Database operation in JIRA fails with "Could not find column <column_name> in previously parsed query" if it didn't help then it is better to reach Atlassian support
-
@Eithan Zand You can reach this goal by following of the below : * You can add yourself in the notification scheme to receive email if any issue related to your project "closed". * You can create subscribe for search result filter which will send notification at your convenient schedule but not once issue status changed to…
-
If i were in your position, I would try to perform * Re-Index from the system * Workflow Integrity check from DB
-
ok, now we found the problem and you need to update the resolution field for all closed issues if you have scriptrunner then it is easy task as there is a built-in function to update the resolution based on filter. if you don't have it you can update it by following the instruction here: HowTo: Bulk Edit Resolution Note :…
-
@PaoloDiBello don’t worry, we are here to support each other. please try to use this jql and find if there is any data retrieved resolution = unresolved and status = closed If there is result it means the issues is closed but not resolved which means it won’t return in the api for CLOSED_REQUESTS
-
@Esther Strom I think your problem exist with the post-fucntion order. as per this Post-function on Create Issue transition appears to not work Cause Any post functions placed after the "Creates issue originally" function will not have updates to the issue persisted to the database. Resolution Re-order the post-functions…
-
@Debbie Dockery This is happens if you allowed "parrallel sprint" in jira configuration. You can disable this feature by visiting Using parallel sprints and the issue will have only one sprint assigned to it.
-
@Bruce Mohler are you sure you need to get list of customfield objects using "getCustomFieldObjectsByName". if you need to get only one customField object you can use getCustomFieldObject(customfiedID) and no need in this case to use first() also second line need to be updated as below def cfLastAssignee =…