Comments
-
"move" is not the same thing as "transition". Check the conditions on your workflow.
-
Because copying things is needless duplication, and generally a bad thing to do. Update the original, you've got a history if you get it wrong. Or include pages from the original if there's a genuine need for a copy. So, to answer the question, no, there's still a reliance on add-ons for a function that you should not…
-
It looks like your installation has not installed all the required files (or some have been removed after install)
-
I don't think "just copying the mdb file" works, you need to do a proper backup and restore of the database. Also, while I suspect you're using the right Java, the screenshot just tells me what the current default is. This is not necessarily the one in use for Confluence. Have a look at the logs as startup is attempted, it…
-
Sorry, yes, I'm assuming an admin is also a user. They won't count towards the licence if they only have admin rights (and logging in is implied by having those rights). But if you don't give them any application access at all, they don't count. They won't be able to see or use anything they configure on a project level…
-
Errors with files usually mean you have the permissions on them incorrect - the user running the service must have full read/write/execute/delete rights on the whole installation, home and temporary directories. I would also want to check that the version of Java it's using is definitely the one you think it is, and that…
-
The rules changed with JIRA 7, which changes the language of what you've been reading quite a bit. However, the basic rule remains "if the user can log in, they count towards the licence". In all versions, access is granted via groups. Before JIRA 7, this was quite a simple one - there was a global permission for "can log…
-
This is a five year old question, so posting here really isn't likely to get you much response. This particular question needs to be asked of support.atlassian.com as soon as possible, before your data goes out of the backup cycles. I'd also want to question why the owner of your Cloud system ignored or did not get the…
-
Repeating the same question does not help us work out what you mean. Please tell us what report it is?
-
Run filters for the various "sprint = X and issuetype = Y" you need and the results will tell you those numbers. I'd also save these filters and use them in dashboards. Another option might be a filter for "all issues" (or variants that you're interested in) used in a "2 dimensional filter stats" gadget with sprint and…
-
Yes, you can, but you need to write add-ons to provide the custom field *types* Start at https://developer.atlassian.com/jiradev/jira-platform/guides/fields/tutorial-creating-a-custom-field-type
-
That's good, it shows 2 of the 3 points are set up right. That means it should be down to the "Field Screen" on the last line. The field might well be on the "Edit" screen for the issue, but is it on the "transition" screen for that transition?
-
I'd start with a look at the proxy logs - is it showing "JIRA Server not responding", or something else? Whatever you find there, I'd still also check the JIRA logs to see what that is doing. And maybe look into performance logging there (but I'd want to rule out the proxy before going into any detail there - no point…
-
>but I can't connect to Jira through browser. That's because it is not starting. The errors you see in the logs are preventing it. If I remember it right, then that error means your Certificate Authority doesn't trust your certificates.…
-
Depends on the context of what you're doing, but there's two basic ones. If you're working inside JIRA, in an add-on, then the API has several simple "give me custom field value from issue X" options. From outside JIRA, a single REST call fetches the whole issue in one step (and if you make it a bit longer, you can ask for…
-
Well, advise is a verb and advice a noun, so as the product of a Grammar school, there's some cognitive dissonance there. But there's no way I'd consider any of your postings as spam. I can't see why the spam filters are picking it up, so I can't really give you any advice on how to avoid the flag. Hopefully, I've managed…
-
Javascript in field descriptions was always a bad idea at best. It was never "supported", ever. It was a bodge that Atlassian gently ignored for a long time, but has, at last, been shut down properly with 6.2 (6.1 mostly stopped it as Jeff says, but there were a couple of tricks)
-
The licence consumption is because JIRA's licence really is counted by user. These people will be using JIRA, so they need to be licenced. If you don't want to consume licences, the only option is "anonymous".
-
You either have to give them the right to log in (which consumes a licence), or start making the project anonymously accessible (Which is a nightmare in terms of tracking, and generally should *never* be anything but read-only)
-
Plug-together workflows would be a really nice thing to have, completely agree with you on that!
-
Jeff, I think the complexity of your answer to get a really simple basic thing proves the point - SQL is by far the worst way to do reporting on JIRA.
-
You already said that, and I've seen all of this before. I've already explained the failures in it above. Not the split column stuff - that's not strictly necessary to do in JIRA, as you can get close to it without the feature, but it would still be a useful thing to have. The failure is the multiple done. It does not…
-
Actually, it works fine. You start by separating projects (which are collections of issues which you're grouping together because they have something in common - even if it's just the desire to have them follow the same processes), from boards (which are for teams). They are totally different things. Take, say, a 10 step…
-
Components are tied to issues via the nodeassociation table. I can't remember the exact definition of the table (and it might vary by version a bit), but there's a source_node_id and sink_node_id field, one is the issue, the other component id, and then there's a sink_node_entity which defines what type of association it…
-
Duplicate of https://community.atlassian.com/t5/Confluence-questions/Unable-to-start-up-Confluence-Fatal-error-during-startup/qaq-p/605918
-
It should indeed follow a best practice, but this particular one is NOT a best practice - it's awfully broken. When you have multiple "done" status, or ones that are subjective, there must be a way to differentiate them clearly at all times. There's nothing wrong with Kanban's idea of different dones within meta-columns,…
-
Start with nodeassociation which links the workflow schemes to projects. Select * from nodeassociation where sink_node_entity = 'WorkflowScheme' and sink_node_id = '123' will give you the basics. The category for projects is in the same table.
-
Jeff is right, it's impossible without rewriting the core of JIRA's admin access scheme. Your users can see a lot of the config from the project headers though.
-
This does not change the fact that putting one status in multiple columns is utter nonsense. When you have multiple "done" status, or ones that are subjective, there must be a way to differentiate them clearly at all times. There's nothing wrong with Kanban's idea of different dones within meta-columns, but it's completely…
-
SQL is absolutely the worst way to get to JIRA data, and should not be used in this way. As a simple example, you now need to join over 40 tables (many of them more than once) just to get the data for a single issue. Do not use SQL to do it. (And, please, when posting questions, drop the use of "as", it does nothing more…