Comments
-
Yes, I understand that, but the script is calling something in "nimblespace" that is not right any more. It's not part of the script runner stuff, so how were you providing the library in the old version and how has it changed in a newer version of it?
-
That's a limitation of html - the brackets need to be escaped in urls, but they can't be used in anchors because the escaped character is not the same as the pages actual name. I'm afraid you are pretty much stuck, unless your company changes its policy to match internet standards (not using escaped characters in titles)
-
Yes, and see https://community.atlassian.com/t5/JIRA-questions/Multiple-sub-tasks-in-paralell/qaq-p/578162 for how.
-
Yes, that's one of the things sub-tasks will do for you. Each of the lines beneath "feature" is a sub-task, with its own workflow.
-
This is basically the same question you asked yesterday, which has similar answers. See https://community.atlassian.com/t5/JIRA-questions/Multiple-sub-tasks-in-paralell/qaq-p/578162
-
Usually means JIRA is not running. You'll need to (re)start it, and then check the logs to see why it's not running if the problem continues.
-
You will need a little bit of code to do it. You can create a validator on the "create issue" transition that can search for "project = current project and issuetype = project-description" and if the size of that is larger than zero, fail validation.
-
I would not recommend it. It might work, but I've had lots of problems. A better option would be to upgrade to 7.0, then 7.latest, but that can still be flaky. The best option is to upgrade to 6.4.latest in full, then jump to 7.latest. The supported route is 6.4, 7.0, 7.latest. But generally 6.4 to 7.3 seems to be working…
-
I think you need to explain what this has to do with Atlassian products.
-
Ok, if the indexing is still running, what is the problem?
-
Define what you mean by "access"? Read it? If so, then yes, have a look at the JIRA macros in Confluence.
-
None of these options are quite right on their own * Properties will just stop everything being editable by a group or groups (or roles etc), but not on the transition screen because it's not an edit, it's a transition * Conditions will stop the transition being available to the users * You can remove a field from the…
-
It wouldn't make sense to redirect someone when they click on a page title on the tree - the whole point of it is that it should take you to the page the user has asked for. You say you are using an iframe to display another page in a page, that really is a horrible way to try to show content. Try the "include page" or…
-
You should amend your board filter so that it does not include issues until they come within range of the date. For example "duedate < +2w" should exclude anything with a due date further than a fortnight into the future.
-
What do you mean by "import"? Copy it? Or show something in a page that's been drawn in from somewhere in Bitbucket?
-
It is possible, the example you have probably seen at https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-query-issues works fine - it returns a list of issues that match the filter you give it. There's a working example for both get and post on that page, and I…
-
There's also an add-on that gives you "project fields" in the marketplace, you could use one of those for a status. Most of us use a "closed" permission scheme (sometimes hiding the project, but usually just allowing read-only access so no-one can change anything), and often we use the project category to indicate groups…
-
Your JIRA system has a custom field called "site" in the project that your Confluence is trying to create the issue in. It is flagged as mandatory, but Confluence is not providing a value, so it is being rejected as incomplete.
-
None. You will need a production licence for the target restoration system, and I'd recommend a developer licence for the temp server. But there's nothing to save on Cloud, the licence there only applies to the Cloud system and is dropped on export.
-
Yes. Everything except attachments.
-
That's a panel provided by an add-on that is specifically for pulling that add-on's data out into it. If you want to get a custom field into a panel, you'll need to find or write an add-on that provides a panel and draws it in there.
-
Same question as https://community.atlassian.com/t5/Questions/JQL-query-to-combine-status-and-assignee-in-search-condition/qaq-p/578341
-
If one is working and not the other, then there's a really easy question - what is the difference between the two systems? Identical configuration won't work because you have two different servers, which means different config settings and certificates for a start.
-
You don't. You should not be looking at the database, because the absolutely minimum actions you have to take to do this linking involves stopping JIRA and taking a full proven backup before changing it, and then re-indexing after restarting. That's not feasible for running a system that people need to use. Could you…
-
Click on "assignee", or use a post-function that sets it to the reporter on a transition. JIRA doesn't naturally set the assignee when changing issues though, so when you say "instead of default assignee", you are referring to something your admins have set up for you, and that's what needs to be changed.
-
Sounds like some form of failing validation. What does the log file say is happening when you click "update"?
-
com.nimblestorage looks like a class imported from an add-on. You'll need to work out what was providing it and how to replace it.
-
You can write a "service" to run regularly, searches for issues where the field is set and clear it out.
-
Have a look over https://www.atlassian.com/licensing/cloud/ordering or just add them up from the main pricing pages for each product.
-
They're global, they only care about the number of active users.