Comments
-
Dear @Dieter Hoffmeister, you could also give the Jira Suite Utils a try. What you probably need are some workflow post functions. So long Thomas
-
Dear @Jason Everson, you already know, that something different goes wrong, when one issue is shifted for more then 2 times to following sprints, right ;) What you decribed sounds like a bug. Probably there is a hard coded counter for more than 4 removals - I don't know. I recomment, that you contact the Atlassian Support.…
-
Dear @Jason Everson, as I cannot reproduce your behavior on my instance I can just guess for protential reasons: * The issue can be still seen with accessing it in the classic way via issue key, right? * The issue does not appear in the backlog any more, right? * The issue was not resolved, when removed from the sprint,…
-
Dear @Matthew Mallard, for Jira: invest a little time in searching through the community answers. There was more than once written how to go from 6.4.x to the latest - then you will have a clear idea how hard it is. for Confluence: upgrading is a straigth forward prcoess. Reading upgrade notes. Not too big deal. Ways…
-
Dear @DD Perea, not a big deal. Refer to the rest api doc and fire a get request on specific attachment. The tricky thing will be to locate the right attachment. The endpoint is always the same because there is only one api entpoint per instance. You could wrap a proxy around to differ between internal and extrenal. So…
-
Dear @Joe Gormley _IT _ Release Mgmt_, just tried to replicate what you described and found out following: The first time when I drop an attachment into a comment a link is created and the attachment is saved in the section. Adding new versions of the same file (fiilename is same) will make the previous created link to…
-
Dear @Burak Kocak, first of all, you should not use Jira 6.4.14 anymore. With the information you gave its hard to help. I just can give you some hints that show directions: * your permissions are not sufficient to continue - check your permissions * a mixture of different issue types of different projects doesn't allow…
-
Dear @Martin Kaufmann, best explenation is found here: CONFSERVER-17621 So long Thomas
-
Dear @Yu Fei, then you need to ask Atlassian to add your described funtionality to Jira. I recommend to open a suggestion. Probably a related issue already exists. So long Thomas
-
Dear @Vidya Shevale, afaik you cannot attach files/images to a page that does not exist or in other words, first create a page and then attach the files. And you do not need to send the files base64 encoded - this will do curl for you. Hope that helps. If not, please give me more details of what you exactly do. So long…
-
Dear @TieDall, I have checked the documentation a second time. Base64 is accepted as a MulitPartEntity mesasge. So I guess, that somehow what you send to Jira does not comply to RFC2388. Best you check how for example curl sends attachments to Jira and then reimplement this in your case. If this doesn't work, implement a…
-
Dear @TieDall, you have to envelope your attachment on your own. Jira doesn't process base64 files. So best you decode your attachment and then post them to the API: See my Java snipplet for this: import org.apache.http.client.methods.HttpPost; import org.apache.http.entity.mime.HttpMultipartMode; import…
-
Dear @Jason Everson, can you please tell us, how you removed the issues from the sprint? So long Thomas
-
Dear @Marjorie Pleta, just a suggestion: Is it possible, that the watchers of the former project are not allowed to see the issues of the new project (where they were moved)? So long Thomas
-
Sems like you have a plugin installed, or? Your JQL is not standard Jira.
-
Thanks, @Matheus Fulginiti Schonarth! Did you take a more recent version of Jira than 7.9.0?
-
Thanks, @Matheus Fulginiti Schonarth! Have you used a more up-to-date version of Jira than 7.9.0?
-
Dear @Dennis Gyor, you are right, it's not answering the question. You can assign people to one story. Then export all stories of one sprint to CSV and sum up the story points per assinee. I do not know any dashboard gadget, that could help you in your situation. So long Thomas
-
Dear @Kris Fininen, You can ignore/remove this wrap, but it will appear again and again, automatically. So long Thomas
-
Dear @Raymond Mancy, I recommended not to estimate in SP for bugs, only! I see no problem in estimating in hours/days. Then you can plan your sprint. Or alternatively, as described above: best effort (as much as possible) within a time box. A performance issue is not necessarily a bug. Is a broken non-functional…
-
Dear @Kris Fininen, this is a known bug reported by myself. I discovered it while developing against the REST API. Fell free to vote for it. So long Thomas
-
Dear @Raymond Mancy, the team earns story points for every item (that ideally has a value for the company) they finish within a sprint. This will result in a velocity. A bug is the result of a false implemented user story (to simplify this assumption). If they earn story points for fixing bugs, they get somehow rewarded…
-
Dear @Jean-Marc Frappier a 502 is in most cases a call from nginx to the tomcat port of Jira that does not exist / is not open / is blocked by a firewall. Check with telnet localhost 8080 first in a shell of your server. If the server doesen't respond, then probably Jira is not running, or the port is a different one or…
-
@Jean-Marc Frappier, seems that nginx has a problem in reading the certs. Try to create some self-signed certs for test purpose. If that will work, most probably the certs are corrupted or in a format nginx does not understand. So long Thomas
-
Dear @vivek karn, for the details you get in the JSON response, it's best to explore them on your own with a Rest explorer/client. Not all possible combinations can be found in the documentation. The variations are to huge. But after you have seen some JSONs you will get familiar with the format. So long Thomas
-
Dear @Paul Phillips, thanks for the reply and be that critical. I would really love more would do this! I try to refine what I have written in January: The concequency to avoid measurement is to fully empower a team. Means they are allowed to "fire" team mates - of cause not that easy (there should be a simple process).…
-
Dear @Dominic Price, Which skills (and their levels) are obligatory for an agile coach to be successful in introducing agility to a team/company? So long Thomas
-
Dear @David Yu, the solution with this plugin is fine - but you create another dependency to a 3rd party plugin that could get commercial in the future (have seen this behavior many times). I always try to recommend solutions without extentions, if possible. So long Thomas
-
You are welcome!
-
Dear @Oleksii Okhmush, you can do following: * create a custom field of type user picker (multiple users) * add this to the issues (add to screen) of your project * modify your security level (add this custom field to the level) Now only issues are visible to those users without opening all for visibility. But you have to…