Comments
-
Yes. But only from different boards by default. You can run parallel sprints from the same board if you enable the "run parallel sprints" feature in the admin settings.
-
Sorry for the delay, Euro Summit is quite hectic. My first paragraph isn't too clear on what I was trying to say, so I'll try to rewrite it differently: There is no "project type: scrum/kanban". A project type is a question asked during creation to help you set it up in a particular way, but after creation, it is…
-
There is no way to do this as described. JIRA does not really care if you think a project is Scrum or Kanban, because the project does not have that. Boards are what define the Scrum/Kanban definitions and the boards are not related to projects. You can easily set up a Scrum project and then add a Kanban board that looks…
-
Yes. Each sprint has an independent start/end date.
-
Your workflow doesn't have any way to move back from "ready" or "done". I would add routes back, even if they're limited to the project lead or admins only. For issues that are now stuck without a resolution and can't be pushed back, you have several options, but I would go with one of the more obvious ones: * Edit the…
-
You say you've checked the permissions and ownership, but are you sure the user running JIRA is correct?
-
And the rest of the questions I asked?
-
Create a collection of the ones you want to add and then use projectrolemanager.updateProjectRoleActors.
-
Use a ProjectRoleManager to maintain users and groups in a project.
-
You need to log in as an admin and either make the field optional in the field configuration or add it to the screen so the user can fill it in.
-
There's not enough here to diagnose the problem. If I were doing this, I would drop back on brute force. Reboot the server to get a clean run. If JIRA is set up to start on boot, and tries to, great, what does the log say after the startup? If it's not set up for automatic start, that's also fine, but what does the log say…
-
... and we've moved again. Lithium now.
-
I'm afraid this is a bit of a "circular answer". Your backup is missing data for the field "key", so the project import cannot import it. The reason it is missing is that you've manged to create an export with missing key data. So what you need is a valid backup with that data.
-
This is a networking question rather than a JIRA one, and there are several ways to do it. Whatever you do, the first prerequisite is to have a domain registered and available for your company. The most basic one is to simply make your computer the host for that domain. Of course, that means running on the web server and…
-
Port 8080 should be enough, it exposes JIRA on a single port. Make sure you make it available to the host server too - JIRA needs to talk to itself as though it were an external user. Some add-ons may add other ports when they're for "integrating" with other systems, but that will be covered in the docs for them.
-
Hmm. Whereever you found tha pages that suggested OpenJDK is supported, I'd suggest you stop using them for help and advice because they're wrong. Oracle Java is the only supported one. OpenJDK can work, in some cases, but it is absolutely not supported. Sorry, hit enter too soon: To make it at least try to start the…
-
I'd say this is the stuff of "articles"
-
They call that "Cloud". They're not going to offer Server hosting, it's too potentially messy to be supportable on the scale they want to host it on.
-
Ok, that's fine, but it's not "archiving", it's "completely destroying the issues". You can run filters for "issue last updated before 1st Jan 2017" and then run through bulk-delete for them, but that's only a thousand at a time. I'd script that from the outside, doing it over REST.
-
>The issue here is not about wheather I am able to assign the bug or not It absolutely is about this. Your function is failing because the user is not a valid assignee. It's not an issue, it's not something you can break with a Behaviour or botch. The person you are trying to name as the assignee must be an assignable user.
-
Probably not, unless you're willing to go over every class in it, decompile them and then rewrite the code and make it compatible.
-
Scripted fields only have a "view" template, because users can't put data in them. This tells JIRA that there is nothing to show on screens which need input. There is no way to get them to appear on screens that allow for updates.
-
By rewriting a chunk of Confluence's core code. The /display/ part shows us it's a content page, rather than a functional url. Something is needed there to make that subdivision (or a user could create a page that has the same url as a functional url), and Atlassian have used "display". It would be nice to be able to…
-
Nope, you need the source code. The .jar is compiled code which is referring to librarys that are no longer valid or available. The pom.xml is an instruction on what to do during compilation and later, changing it in the jar is not going to recompile the code. You could try a decompiler, but I would look for the code first.
-
Add-ons need to be licenced at the same tier as the largest number of users you have across the three applications. If, for example, you had 3 Agents, 25 Core users and 50 Software developers, you'd need a 50 user licence for your add-ons. In your case, you can licence software at X users, and Core on 0, and you won't have…
-
No, you'd need a lot of coding to do that. * You need to be able to tell A that "JQL function X means go read another JIRA" * You need some code to go off and do the reading when the function is run * You will need to take the response from B and somehow inject it into the filter * Filters in JIRA return a list of issues.…
-
When you are assigning an issue to someone, it must be someone that is currently allowed to be the assignee. Check the project permissions and amend them so that the target people can be assigned issues in that project.
-
Start with a read through of https://confluence.atlassian.com/adminjiraserver073/upgrading-jira-applications-861253088.html I would recommend upgrading to 6.4 first and then 7.latest.
-
You'll need to install a clean empty copy of 5.4, then you'll be able to restore the export into that.
-
What do you mean by "archive"? You'll need to define what you want that process to do and what effect it has on the issues being archived.