Here is the scenario, some JIRA ticket may be close and reopened several times.
New ---> In progress --> Done ---> ReOpened --> Done ---> ReOpened
Is there any way to query and count how many time's ?
It seems that JQL don't have such kind of function - count()
https://jira.atlassian.com/browse/JRASERVER-65152
Related
I'm wondering if this is possible. I've done some googling, with various different wordings. I've been asked to add to a job that creates a jira ticket when a previous step fails (the previous step is a docker build command). At the moment the jira ticket has no description, and I've been asked to add something meaningful. I thought the stacktrace would be a good start - essentially what you see in Github when you navigate to the failed job. Is it possible to access this like a job output? Or does github provide it some way through the context or something like that?
I have 2 instances of JIRA . I have written a script where tickets from one instance are read and a replicas of same are created in another instance.
Now the problem is , whenever I run the script it is generating duplicate tickets again and again.
How do I prevent this duplication of tickets? Please help.
Ideas:
Create a link field in each Jira issue and populate it. If the field is populated the script should not create a new issue
Use a "last synced" field in the source Jira and only create a new issue if the source issue has not been synced
You don't say but I assumed that this is a one way sync
I have a scenario where a Jenkins build should get triggered automatically only when all the issues under a particular JIRA project are changed to " IN PROGRESS" state. Let's say I have 3 issues under my JIRA project, where 2 of them are in "TO DO" state, and one of them is in " IN PROGRESS" state. A Jenkins build should only be triggered when the remaining 2 tickets also move from "TO DO" to "IN PROGRESS"
I can trigger the Jenkins build automatically for individual issue status change by using the JIRA webhook and JIRA trigger plugin in Jenkins by selecting the option of Build when an issue is updated in JIRA and passing the required parameter in Jenkins job, but I need a condition where build should happen only when all issues(and not just one) for a particular project are updated to " IN PROGRESS" in JIRA. Is it possible to have something like this?
One of the solutions is to use JIRA's REST API and poll every x minutes to check if all issues that match your query are in "IN PROGRESS" status. You can even combine those two - after you receive a call from JIRA's webhook you can respond by calling REST API to check statuses.
I've had a user mark the entire dev branch for deletion, they then attempted to revert / undo these changes but it just hangs. There are 14 million items stuck in their pending changes.
All of the tf undo, tf remove workspace, commands time out. Is there anyway to remove the lock that is preventing other users from checking in their code?
I can see the PendingChanges for that user in the TFS database but don't know if I can just remove them or what other tables hold the Locks?
For the timeout exception, you could update the tf.exe.config or devenv.exe.config file with the following configuration values:
<system.net>
<connectionManagement>
<add address="*" maxconnection="1000"/>
</connectionManagement>
</system.net>
After set the limit to 1000 on your side, then try to undo individual projects like jessehouwing suggested, also keep watching the value in Resource Monitor,.
I was able to create the new job but I am NOT able to add any build step.
This behaviour is reproducible and it occurs when I try to do it from the initial “configure” page I get after job creation as well as with a later configure attempt. And its persists for all job types.
It does not depend on whether I am logged in or not.
The problem is that when I open the “add build step” I get a selection of possible job types (“shell script”, “windows batch”, …) but when I select one of those nothing more happens.
I also have other jobs of this type already up and running and I am also not able to add more build steps to those.
I had this with v1.625.3, all of a sudden. Problem in Chrome and FF. Workaround was to use IE.