Comments
-
A flower is a good thing to hide behind :-) Well done on the new job!
-
Correct - a scripted field in scriptrunner can be really simple, I suspect it can be done in one line of code for counting labels.
-
You'll need to examine each permission scheme to see what the rules are. Then check the membership of each project is correct, removing the unwanted access and replacing it with users and groups as appropriate.
-
Ok, then you should grab a backup of the 5.1, migrate it on to a temporary development server, upgrade it to 6.4, then hand your new hosts an import. (Or, better, get them to do the upgrade, but I'm guessing that's not an option)
-
This error is usually caused by the Confluence user for the database not having the full permissions it needs in the database. Could you check that it has complete access to that one database (create, drop, index, grant, etc)? I would not recommend messing with the memory until you *know* it is that. There's nothing in…
-
I'm afraid you would need to rewrite the code that lays out the view screen.
-
Confluence does not have a folder approach to file attachments. You attach files to a page and that's it. If you want to do uploads via a folder, you could explore the WebDav functions, but you are still going to need to think about how you want to do the folder nesting (my instinct is 1 page per folder, but I don't know…
-
Building an XSLT to do that is going to be 1,000 times more complex than upgrading a 5.1 install via the recommended and supported routes. What makes you say it is "not upgradable"? I have to seriously question that because today, my colleague and I took a 5.1 installation to 6.4, three times (errors down to hardware and…
-
You are going to need to explain that more clearly.
-
I'm pretty sure you could do that, but you will need to do it in the core menu code.
-
We're a community of end users, not Atlassian. As such, we mostly know as much as you do about Atlassian plans. But, um, what makes you think it's not already there?
-
Since my previous answer, I've met a couple of Cuban developers using Bitbucket, so the answer is "yes". I suspect they are using VPNs or other methods to circumvent the pointlessly idiotic and annoying US and Cuban controls.
-
I think you need to explain this more - what has a paper jam got to do with Bitbucket?
-
What function? Probably worth asking about it properly as a new question.
-
Good. You don't want to be connecting to the database directly, it's a really bad idea, and the single worst possible way to get to Jira data. Could you explain what you are trying to do so we can help you with the right way to use Jira?
-
You will need to amend the core code that provides the menu.
-
Have you read the "how can I resolve this?" link?
-
You only have "create blog" permissions in that space. Talk to the space admins about getting page permissions.
-
There is no relationship. Time tracking is a record of estimated time worked and actual. Story points are a measure of complexity. A burndown chart can be told to use one of them (or another number) to track how you're doing. Subtasks are irrelevant to burndown - they are a convenience for developers to break down a story,…
-
It depends on your user directory. If it's the internal one, yes, Admins can add users, but you can set it up for people to sign up themselves.
-
"Unable to browse" tells us nothing. What is the error?
-
No, you need to do the full set of revisions. But you can use groups to allow large batches of users in.
-
The "ugly" option is to put an impossible validator on the create transition. From the user's point of view, this goes: * I click "create issue" because I think something needs doing * I fill in a form with several fields, including one where I write an essay that explains the problem in detail * I click "create" * I get…
-
I'm afraid the short answer is "no". If someone can create an issue in a project, then they can create any type of issue. Some add-ons can provide you with some ways to block creation, and the behaviours module in Script Runner can be a bit more clever and remove the option to create the "wrong" issue type in some places,…
-
Please bear in mind that however you do this, you will annoy your users, as you will be destroying the summary they entered on creation.
-
"Move all subtasks" is not a native Jira function, so I suspect you had an add-on providing it. I'm sorry, but I can't find an add-on that might do it in the marketplace, so I think I'd want to ask your admins what was providing it before.
-
There's nothing to tell you about modules themselves, but have a look in the Script Runner admin section for "Script Registry", which tries to list all the places you've used it.
-
I am going to guess that this is a Cloud system? If so, I'm sorry, but you cannot (yet) change Cloud urls. Your only option is to buy a new Cloud url and use that instead of the incorrect one, and let the incorrect one lapse - it will die a week after you stop paying. If it's a recent mistake, Atlassian may refund you on…
-
You're doing it wrong.... Nah, you're not in the slightest. Jira doesn't support this directly because it's not generally done with "multiple backlogs" (they're confusing and messy). The "take x% technical debt in each sprint" is a great thing to do, and I wish more people did it. The usual approach is to have a clear…
-
Ack, sorry, scratch that, I forgot they changed it and made it less useful. Go to the downloads page instead (https://www.atlassian.com/software/jira/core/download for Core for example), click on the link for other versions, then "view all versions", then you have to click on the totally unintuitive 7.0 to get a drop-down…