Comments
-
Dear @boardtc, I opened a request for you. As soon I got feedback, I will let you know. So long Thomas
-
Dear @anissa mekki, your question is best answered on Developer Community. Please raise there a new Question (not Discussion). So long Thomas
-
As I wrote - JQL lacks the ability of wildcard search.
-
Dear @Domagoj Zecevic, have you tried: project = "TST" AND (summary ~ "field" AND summary ~ "check") worked for me. EDIT: what you would required is "*field*" but this is not implemented in JQL, yet. First letters are not allowed to be '?' or '*'. So long Thomas
-
Dear @Danyal Iqbal, this is the default behaviour. All fields present on the view screen are sent. You need to parse the JSON and select only the fields you need. you can read in the upper reply of CRM Support, that it isn't the case, otherwise the whole question would be obsolete. Please post only information that will…
-
Dear @Francesco Mazza, this is a matter how often such requirements are requested. Have a look at https://jira.atlassian.com. Search for your subject - eventually someone raised it already - then vote. Otherwise create an on suggestion. So long Thomas
-
Dear @Umed Kumar, you would like to disable drag&drop for some issue types in your agile board? * go to configure board - General Tab * there is a filter setting. * modify the filter so that only issue types are included, you want to drag and drop on the board. Alternatively you can * modify the Issue Type Scheme of your…
-
Dear @CRM Support, if this is the response, there is not really a lot of information inside, or? The response should look like this example response: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/issue-getIssue Have you tried to expand=renderedFields,names,schema,operation So long Thomas
-
Dear @Dustin, you have to add headers: "Content-Type", "application/json" "accept", "application/json" "X-Atlassian-Token", "nocheck" So long Thomas
-
I see. This multiple boards on one project is often a source of troubles. It's for me hard to get a clear picture of your current configuration. So any advice will just be a try. I recommend to separate these multiple products within one project as good as possible, means an issue should not appear on two boards the same…
-
Dear @Dustin, can you please post the JSON errorMessage? So long Thomas
-
Dear @Evan Ramos, you gotta chance with modifying the email templates. So long Thomas
-
Dear @Jacek Skrobisz, I would suggest to contact the vendor of this plugin - they should know the details. So long Thomas
-
Dear @Edward Basiliere, ok - this 'could' be the reason (just guessing): The vendor hasn't thought on the API, so Jira doesn't know in the moment of the REST call, that this should be executed. In general, when a plugin provides REST functionality, there will be a documentation. Eg. see the API for Zephyr. Best you ask the…
-
Dear @Susan Williams, so you only use Kanban and nothing else? No second Agile Board on the same project? No modifications to the workflow schemes and issue type schemes? So long Thomas
-
Dear @Tanner Tuttle, have a look at this article about JQL function. The interesting one for you could be openedSprints() and closedSprints(). BtW: that the issue is in two sprints is fine, it was once committed to be done in sprint 10 - so it counts to the report. So long Thomas
-
Dear @Edward Basiliere, this sounds like a bug. Are these post-functions provided by a plugin? Or is from standard Jira? So long Thomas
-
Dear @Susan Williams, I can imagine that all the questions are confusing. We should wipe there a little bit ;) For Scrum Boards: In the backlog you will see only stories. And epics on the left side. Sub-tasks if stories are only shown as soon as a story is on the agile board (current sprint), by default. In Kanban mode,…
-
Dear @CRM Support, additionally to the 'fields' param you have to use the 'expand' param. API tries always to send as less as possible. Which fields would you expect in the JSON response? So long Thomas
-
Dear @Tina Holmes, afaik you can't do with Jira (out-of-the-box). I also think (I didn't search on marketplace) that there will be any plugin that can do. But this is what you an do as a work-a-round: * Export your current issues to a CSV file * Eliminate all columns except the labels column and save as CSV (native text,…
-
@Tim Burgess, have you tried to connect to something different instead of Jenkins, eg. another web service or just a netcat listener, to see if anything is incoming? nc -l 443 (done on destination host) So long Thomas
-
Dear @Chen_Touboul, a) unfortunately not. This is not recommended by Atlassian. You can try but at your own risk. b) if the dump is from version 7.2.4 >= x >= 7.0.x, then you can. The path is 6.4.14 -> 7.0.11 -> 7.2.4. But you do not need to restore from XML file, you can just point the new Jira version to the current Jira…
-
Dear @Kavitha Yeleti, apart form your assumption is right, can you reach from the Jira Server https://marketplace.atlassian.com? Check this with wget | curl on command line, please. And it could be also disabled. There is a "Setting" link at the bottom of the find new add-ons page. So long Thomas
-
Dear @tim.stauffer, I think the data from the sync is still for Fisheye "available". Best you remove the external user directory completely. I don't know, if a restart is required, but it my not harm Fisheye. So long Thomas
-
Dear @CRM Support <-- nice name, have you checked parameter "navigable": By default, all (*all) fields are returned in this get-issue resource. Note: the default is different when doing a jql search -- the default there is just navigable fields (*navigable). So long Thomas
-
Dear @Jenny Mattson, can you please make a screen shot - that will easy up things. So long Thomas
-
Dear @imfilipe, a total different approach: filter the URLs for specific IPs and spaces with a proxy in front of Confluence. Will definitely cost less time than coding a plugin. So long Thomas
-
Ah - sorry. So I guess, you have searched the marketplace already. I do not know about a solution for this, but you could do following: * get the source code of Jira and make your way * use the REST API and send emails on your own So long Thomas
-
Dear @janisse eichstädt, this can vary form Jira project to project. Have a look at your Notification Scheme, that the current project is using. On this page you will find more information. So long Thomas
-
Dear @Alexander Volkov, from "what" do you get 401? Jira itself? Is this error is in the log file? So long Thomas