JamieA Expert

If you want it displayed in the changelog you should probably use a real field, and update it in a listener.

I don;t think you want to store in the change history the value of a calculated field. What's the purpose, to see how the story effort changed over time?

Can you format your code using the {code} macro so that it's readable. Please add some logging so you know that it's being executed at all first, eg log the value that it's going to set.

See https://jira.atlassian.com/browse/JRA-7020

Yes, those columns should have been added on upgrading. Try dropping all the tables in the test db and do another import, and keep the log. If there are any problems you can investigate them.

If you're not sure about your condition, test the different clauses separately. If you just want to check the text field has a value use: cfValues['Customer Impact'] I think that is all you need.

But you hadn't added your comment when I wrote that ;-) And the link in the link was from me. How circular ;-)

I don't think any link event is raised... Vote for https://jira.atlassian.com/browse/JRA-8505

Hrm... database trigger? Which writes links to some additional table. You have a service that processes each links then deletes them from the additional table. Just a thought.

http://docs.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/issue/MutableIssue.html Issue security is a known issue that will be fixed soon: https://studio.plugins.atlassian.com/browse/GRV-94 However it will only work if the target project shares the same issue security scheme. Labels, you should be able to…

Not sure if you're reading the right thing... you need to set jira up as a user server. Information here: http://confluence.atlassian.com/display/DOC/Connecting+to+Crowd+or+JIRA+for+User+Management

Looks like the same code from my answer here: https://answers.atlassian.com/questions/38542/how-to-check-if-the-login-user-is-a-jira-administrator-using-a-rest-call

Most probably it is their reverse proxy (nginx) timing out... but they should change the timeout message to something sensible.

I see the same general issue with the marketplace REST API - if you do something wrong you get the "down for maintenance" message. If it's a 500, it should say so, not give this message.

Whether the current day is a Monday? That seems like a solved problem, unless I'm missing something. Eg http://stackoverflow.com/questions/5270272/how-to-determine-day-of-week-by-passing-specific-date

This is very similar to https://answers.atlassian.com/questions/38755130 - you could see my gist there. The code is much simpler though - if it's a Monday, just subtract 3 days instead of one. Business holidays are a whole different world of pain - depends on your region etc.

Stop asking the same question!

I don't see why it will be so difficult. If you index something you also index it on the other nodes. It's the same database at the backend. Also, this is not going to be free - my guess is each node will be the same price as jira, therefore the support you get will be commensurate with that. BTW, you should be a bit more…

Quite likely this problem: https://jira.atlassian.com/browse/JRA-40942

For adding steps you need to deactivate the workflow, but for adding/editing actions a draft is the way to go.

Sorry, would have cloned if you had been using hg ;-)

I think it's a bug in Joe's code. I've posted a possible fix here: https://jira.atlassian.com/browse/CONF-24358?focusedCommentId=412365&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-412365 Thanks Jozef for the pointer to the login() method.

I am using his code almost exact as is... Apache sets the remoteuser on the request which is passed to confluence via ajp. His example is for pretty much exactly that. I am not overriding the login method. Previously I was and rememberme worked, but all the method did was call super then add the user to the…

Yes, you only need upgrade to the latest, except for some very rare circumstances, in which case the release notes for every release will tell you.

What have you tried so far?

The issue is fixed: https://jamieechlin.atlassian.net/browse/GRV-705

https://jamieechlin.atlassian.net/browse/GRV-705, fixed in next release.

I agree with that but I think your premise that this is a correct use of calculated fields is wrong. Reindexing issues periodically or when some external value may have changed is not very scalable. I'd consider custom JQL functions or some custom report... 

You cannot make any modifications within a calculated field... the only thing you can do is pull information from the current issue, or other issues, or outside of the JIRA environment altogether, and display it. When JIRA reindxes an issue it gets the value from all custom fields. In your case, that act reindexes the…

issue.assigneeId = "someone" but you need to give more context, I don't know if you're using IssueService or what all.