Comments
-
A column is a selection of issues based on their status. Status is an indicator of where an issue is in the workflow. The workflow is a project setting. A workflow is a collection of status, and a set of transitions that join them together, so that people can move issues from one status to another. If you want to stop…
-
I just edited your question (title and first paragraph) because it made no sense, and I am hoping that you can get a more useful answer by explaining the problem in "JIRA speak". Columns and Swimlanes are very different things. I think you have a good question here, but have not been clear on how you are using columns and…
-
I'm not sure I understand what you are looking for here, but there's no "new feature" I can see. JIRA has supported sub-task issues since version 2, back in the early 2000's (possibly version 1, but I have very little experience with Jira 1, so don't know)
-
No, there is no "other way". Do it the proper way - add "bug" as a sub-task type, then add the issue type into your project's "issue type scheme" (you need to be an admin to do those two steps)
-
What is the new error message?
-
Not sure where you got "parentID" from, but it's not going to work because you might not have it until later if you are running this on "create" Try using the issue object for the parent: newSubTask.setParentObject(issue)
-
First line of your catalina.out is the answer - your server.xml is invalid and unreadable. The <host> element is terminated incorrectly. Try opening it with an editor that knows how to highlight xml (and hence see its structure and errors)
-
ok, that means Crowd is not available on the url in the first line. I don't know if it's the internal crowd or external one you are using?
-
"It's throwing error" tells us nothing. What error? Why did you remove the JIRA home directory to try to fix it? The proper commends to do this are given in the document you referred to. You need to tell us what you're doing differently.
-
You won't get anything from changing OS, if anything, Windows is harder to make work. If you had it working before and then changed something, then undid the change and it doesn't work, then you must have missed changing something back.
-
There are a lot of reasons that might happen, it's just that the majority are "inconsistent index". So we recommend that first, and follow up in the minority cases where it doesn't. Now Cloud (allegedly) has that fixed, there's not a lot else to do on the end-user side. All we can do is report disrepancies to Cloud…
-
You've got swimlanes by story selected. From where your arrow is, but if you're struggling, try a different board with different swimlanes
-
I can't really expand on that. You pick it up and drag it, the same way you do for tasks. If you can't drop it into a column, your workflow does not allow for it - as I said "either there is no transition for it, or conditions are blocking you"
-
You could script something with REST that grabs the issue and parses the history. It's the same as a "check the history tab", but a computer would be able to pull out specifics a lot more quickly than a human.
-
Atlassian don't notify Cloud users of minor improvements like this individually, it's too small to warrant it.
-
There's nothing wrong there. As I said before, "status is not a field"
-
Not sure there's a doc, but it's pretty much the same place. When you log in as an admin, go to the three tabs (My defaults, filter, system), and click system, then a "restore defaults" will appear for that (along with a warning that you may affect all users). That will reset the system defaults completely.
-
Ah, you tagged the question with "JIRA Core", which has all those functions. Trello does not, you'll have to do each one separately (or find a powerup)
-
Wow, you really want to cause yourself massive pains of migration because a service provider is too short-sighted or ill-equipped to provide a single, standard configuration setting? Please forgive me for being harsh, but that sounds more than a little bit daft. Seriously. Finding a better service provider, even though you…
-
Use the issue search to identify them (issues -> search), then look for "bulk edit" on the tools drop down (...)
-
Yes, you need to use a database that is configured to meet the requirements. See https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html to see how to move on to a correctly configured database.
-
Yes the "Logs" I mean are the issue histories, which are not editable without database access or broken scripts. I usually disallow delete which would destroy them. You would have to trust your administrators to not allow those things to be done. But, having said that, it's the same with Sharepoint - your admins can still…
-
I understand it perfectly, Gareth's project was not using the workflow he thought it was. I don't see what you think I am not understanding here. On your questions 1. You drag it. Or click the workflow actions on the issue view. If you can't drag it or there are no appropriate workflow actions showing, then your workflow…
-
Seems pointless, as JIRA keeps all the logs already, and no-one reads sharepoint stuff, and most exports of JIRA data tend not to include everything. But, no, you're slightly stuck on Cloud. The best option is a third service - a simple script can read JIRA over REST for all the issue data (including history), and I…
-
You can't avoid the check. The setting is *mandatory* for newer versions of confluence. Confluence will fail without the correct setting. Your hosting provider *must* change it.
-
Ah, right. It is theoretically possible to run a set of databases differently, so it can be possible to set up one database with Innodb as the default and leave the *global* default as MyIsam, which gives you this as a warning. It's rare to do this, I'm only familiar with the global flag. However in your case, it's set…
-
You are going to need your hosting provider to change the MySQL settings (For at least your Atlassian applications, if not the whole thing)
-
JIRA Administrators don't need it any more, so it has been removed. The index code has been improved so that the changes a JIRA admin makes that need indexing are either done automatically or not needed any more. System admins can still do it, but they are Atlassian support on Cloud system.
-
Possibly. I can't tell without the information about the symptoms I asked for before.
-
<sigh> First hit on any search is https://confluence.atlassian.com/doc/upgrading-confluence-4578.html Which leads to the full documentation