Comments
-
I have the converse, I don't get emails for lots of tags I favourited.
-
You need to check that your workflow actually fires those events. That happens in the default workflow, but if you create one from scratch it doesn't necessarily include those events. Just setting a resolution, or transitioning to a status called "Closed", won't fire either of those events in of itself. Compare with the…
-
A groovy script to do this which you can run in the admin panel: (componentManager.projectManager.projectObjects*.lead).unique()*.name You should be able to paste the output into the roles textarea.
-
Ouch... You can't skip revisions, but you can add an exclude rule for branches/subfolder. And then reindex from scratch. Fisheye fail.
-
Did you find the culprit?
-
Apart from Bonfire, greenhopper will do it, possibly by default if you enable labs mode. You can turn it off though. If you paste up your full plugin list I'm sure someone will know which is the culprit.
-
It requires a js resource on every page but there is no call to GA. Bonfire uses GA by default, which annoys me. I think you should have to opt-in not opt-out to tracking.
-
Yes, it will be a plugin. Like I say, Bonfire does this, but if you don't use Bonfire it could be any other. It's none of mine though, I promise!
-
For some reason I didn't see this answer, or if I did it got substantially elaborated and I didn't get an email about that. Thanks Joseph, that is a wealth of information. I noticed from your chart that Nic is out of control, someone must stop him NOW!
-
I am surprised too. The labelling is my biggest bugbear with the new system.
-
It's not just that they are using us to report issues, because I agree with you, most of the issues are obvious. But they will be doing A-B testing and generally screwing with our minds. At least they should be, given they have this massive captive audience of testers. People that make our money by knowing Atlassian tools…
-
I agree with you, more or less. Personally I don't mind being co-opted into doing testing their product, it makes sound business sense after all. But for that to work, the Atlassian side of the deal is to fix things that are clearly broken, quickly.
-
Thanks Dennis. I should have presented that in a bad-news-sandwich like Radu suggested, wasn't meaning to give the impression that it's all bad. If my two issues I outlined are dealt with properly, I will be a happy bunny; my third issue is way below those in terms of importance to me. And it's great that CQ seems like a…
-
This is https://jamieechlin.atlassian.net/browse/GRV-261
-
It only supports certain types of fields... fields from plugins are generally not supported. You can probably make the change in the database, speak to the fine people at Kepler to check.
-
It's not clear how you are creating the issue - also you appear to be modifying the current issue...?
-
You created a ticket, when I update the ticket jira will mail you.
-
yeah, i'll get to it.
-
What's the actual query you tried with dateCompare? It should work. What's the error? Don't you think that actually putting the error in the question and saving me asking you for it is appropriate?
-
Hi... I don't use Crowd. But seems to me that this configuration should be supported by Atlassian... I've never heard of a different cookie per page, but from your description it sounds somehow feasible.
-
You've configured something incorrectly... difficult to know what without more information. Eg what version of jira do you have, have you customised any files named seraph*, do you have any custom SSO, are you proxying through apache...?
-
Can't you refer to the attachment using the page name, ie SomePage^file.xls, then have it on both pages using the {include} macro?
-
The None should have a value of -1 if it's the same "None" option as the usual one. Or have you put in 00000 just for an example? I'm reading your question... the map key is the value of the option, not the order. Anyway, I think there's an outstanding issue regarding ordering of the options... it's probably down to the…
-
See changelog.vm: #foreach ($changeitem in $changelog.getRelated("ChildChangeItem"))
-
This question is too vague, you should not post masses of code, just the interesting bit. Your other question is better and seems like it replaces this one.
-
Hi Penny, Can't believe you did that at 2am ;-) And using a URLConnection rather than http-builder or the like is hard-core! cheers, jamie
-
Move Issue fires an event, so you could use a script listener to listen for that. I'm not sure whether you should listen on the source or target project, probably target.
-
Not possible atm - you can enter an RFE if you like: https://jamieechlin.atlassian.net/browse/GRV - or make the customisation yourself.
-
As Renjith said, you can use some javascript to do it or maybe modify the template. The behaviours plugin can do this although I'm holding off recommending that for the moment, but the jaascript is sthg like: docRoot.find("#commentLevel option[value='" + setValue + "']").attr("selected", "selected"); You need to check the…
-
Yep, check the project key or name... issue.projectObject.key == "ABC" || what you have already