Comments
-
You've got two accounts with different access rights now, that's why you see different repositories.
-
You can't do this on Cloud, you are stuck with the "new UI" and can't go back to the more usable Server layout. On Server, Jira 5+ has the layout are asking for, but the new icons, fonts and so-on don't kick in until 7.10. 7.9 has the good layout, but older look and feel.
-
Problem is the pages are not static, they're generated. So it can't know what to put in the Tomcat cache until the request arrives, that's why there's no pre-set for it. But yes, a simple hit will cache a whole load of stuff that will get reused. * Yes, I'd hit an issue that you know is always going to be there. * It's…
-
Your "scientist mode" simply means "the number is too long to write out" - in the variable, it's still an exact floating point number. I suspect your script is taking it as though it's a string though, instead of a number, which won't work. What is the data in this field? (Not the value, but what exactly is it for? Why is…
-
The config of Tempo in the target project is incompatible with the data on the issue you are moving. This is why scripting "move" is a bad answer to a broken process - you either need to be 100% certain that the source and target projects have identical configuration in all aspects, or you need to validate and amend as its…
-
Looks to me like they logged work, then had their account deactivated.
-
It's a bit of a hang-over from Jira 1 to be honest. In there, the workflow was fixed, but needed a way to control who could resolve and close issues. So the permissions for "resolve issue" and "close issue" were created and used in conditions on the resolve and close transitions. When we got the ability to edit our own…
-
Almost everything could be failing, it's impossible to tell without the full error, but at a guess by just looking at your code, I'd say the iterator is not finding the new issue type, or if it is, it's not valid for the project you're in.
-
It is because of the caching. The only way to populate the caches is to hit the UI with a browser, which you could script, I think.
-
No, the backup is an export of everything. You will need to import it into a temporary development Jira, delete the projects you don't want to transfer, then export from there and give them that export.
-
You can't do this. Resolution always has a default value and is always set when it is placed on a screen that allows edits of fields.
-
Ok, you will need to work your way through the "supported platforms" docs for each version until you find the last one to support it. From memory, 7.0 does, but 7.10 definitely does not, so support was dropped somewhere between them.
-
Support for MS-SQL 2008 was dropped around Jira 7.3. You need to move to a supported version immediately.
-
This is one of the reasons I tell people not to try it. issue.setStatus is only for *new* issues. You can't just stick a status on an existing issue, you have to transition it. If you look through the Jira code for "move issue", you will find that when it detects that the target status is different to the current status,…
-
Jira Software is an application that you add to a Jira Core. (There is a Jira Software installer, which is probably what you used to create your server - this is not really any different - it installs Core and adds Software, just as a bundle instead of two installs). So, what you have here is a Core system that used to…
-
Business boards take all their config direct from your project settings. There's no way to change the implied sort order in the board.
-
What are you trying to do when you say "open"?
-
You should not use the same licence. You should have a single (commercial) licence for your Production Confluence, and then use the associated "developer" licence for all your test, development, fail-over and backup confluence systems.
-
The two black ones were mine, but they're both dead now. Much as that sounds bad, I think 16 and 18 years of them not leaving me meant I got something right. Heck, Esk (at the front) made it into a keynote presentation at the US Summit in 2017. The one in the middle is a lot younger, and still with me. But I can't call her…
-
Not got much for "funniest" past this "Lazercats are go" photo
-
It might. * You could use one field configuration for them. * You could use several field configurations, based on project. * You could use several field configurations based on issue type. * You could use several field configurations based on project and issue type. In all of those cases, you could do the "different set…
-
I'm English, and live in the UK, so the 4th July to me was "Wednesday". But here's last week instead. For those of you who don't know England too well, this is remarkable because: * It's in "the North", where "It's grim" * It's not raining * The temperature is over 305K (about 90F) * I was not wearing an Atlassian or…
-
Could you just explain how the numbers are sorting? (In lieu of screenshots) e.g. given 1, 4, 12, 16, 105, when you run JQL like "my-number-field is not empty order by my-number-field ASC", what order do you get out?
-
Ah, this could be quite complex. The minimum number of field configurations you need is just one. This is because you could change the fields used in other ways. Imagine you have a single custom field called MyField. You could make it shown in one issue type/project and hidden in another by: * Having two field…
-
You'll need to read the log file to diagnose that. <jira home>/logs/atlassian-jira.log is the one you need.
-
You need to have a read of the Confluence application log - it looks like the Tomcat is starting up fine, but the plugin you have compiled is preventing Confluence from starting within that. There should be details within the application log about that.
-
You need to look at the workflow and check that it has transitions that allow you to go "back". If it does not, or you cannot see these transitions, talk to your administrators - they need to add the transitions for you and/or check the conditions to ensure you can use them.
-
Your thoughts are correct. The Cloud package is always "latest", with a slight minor-release lag across the estate as Atlassian roll out newer versions in blocks of systems, rather than everyone at the same time. The Applications (Service Desk and Software) have retained their internal numbering schemes, but again are…
-
Ah, I see. No, I'm afraid that functionality has not made it to the multi-user-picker yet. There's an open request for it somewhere, but not in my bookmarks.
-
It's not logically wrong, it's been designed that way to avoid the problem of clashes in id. And it's irrelevant to the users.