Comments
-
That box makes it absolutely clear that you will be destroying your data, without any backup. I can't work out any way of getting out of that box - someone clicked "deactivate" and typed in the word (Yes, I've just tried it, you can't not see that box) Deactivating an add-on (or "app" as they now are) is a lot easier, and…
-
Good grief, that's been a massive waste of your time, there are so many faster, better and clearer ways of doing that. But, you've gone a long way, so you may as well finish it this way. You'll need to read customfieldoption and optionconfiguration, along with some of the tables starting with fieldconfig and fieldlayout
-
Use issue links. First one needs to be done with the "more" menu, where you'll find "add link". Once the first one is there, the issue will display it in a "links" panel which has an "add new link" button
-
Best bet is to drop the html onto a web server, and copy and paste the view of it from a browser
-
There is no way "clearing out plugins" will do this. Something else went wrong, but the only people who can help you here is Atlassian support, because they need to read logs to work out what. I imagine that they've said what happened in the support request.
-
Options is the table, but don't. Jira's database is not designed to be read outside the API, and reading it with SQL is always the wrong way to do it. What are you trying to do for your users here?
-
To clarify this a bit (I hope) * Edit permission grants the right to edit issues. The whole issue. * When you edit an issue, you are presented with a screen, which is a list of fields. * If a field is on this screen, you can edit the contents, either with the edit function, or inline, in the issue view directly. * If a…
-
No, they do not go to sleep. There's throttling so it doesn't get overwhelmed, but the service doesn't sleep.
-
Because it determines what options you might have for recovery and who has to take responsibility for restoration.
-
I think Monique may already have this one (not technically a selfie I guess, but those are all rubbish)
-
Hard to say without knowing what the error messages are - the ones on screen are generally not a lot of use when this happens, could you take a look at the log?
-
If you need to enforce it, then you will need to move the edit functions into the workflow - remove the fields from the edit screen and place them on a transition screen, then have transitions that allow limited sets of users to go through the screens (using conditions on the transitions)
-
That's not something standarard Jira fields do, so I suspect it's coming from an add-on. The type of custom field should tell us which one.
-
The list of people in the assignee field is determined by your permission scheme for the project. Look in there for the line "assignable user". That's it really. We can't answer your questions in any detail because you have not told us what rules you have set up for "assignable user" or what you mean by "on that project".
-
I can't work out a way that plugins could deactivate a site. I think when it comes to recovery, we need to know more detail on what happened.
-
If you set up the account, you are the one who has the highest level of access you can get on Jira. You do not get "system" admin, that is for Atlassian only.
-
Duplicate of https://community.atlassian.com/t5/JIRA-questions/IMPROPER-AND-NEW-LANGUAGE-IN-JIRA-DASHBAORDS-AND-USERS-LOGIN/qaq-p/635457#M209448
-
To get this option, you must be a board administrator with a board that has had "simplified workflow" applied to it, by a full administrator.
-
Do not alter the database directly. As you say, there are caching issues, but it's not just the cache you need to worry about, and data may be written back destroying your change. Your cache change may also cause problems, although it won't corrupt data. If you insist on doing this with SQL, then you must have Confluence…
-
This usually means that you have run the service as the wrong user (I usually manage to do it with root). That user has taken ownership of files and directories in the system and made tehm unusable by other users. You've then probably restarted it as the right user, who can no longer get to all the fiels it needs. Check…
-
Run a filter for the issues you are interested in, then use it on a dashboard gadget. Filter statistics is probably going to tell you the most - if you select "status" as the statistic, it will list all status and the number of issues in each,.
-
If you want to use Cloud Confluence, then you get the latest version. Cloud is almost always ahead of Server and you have no say over the version. A trial will simply expire after 7 days if you don't pay. For server, have a look at the downloads page and look for the "archive versions" link. You'll be able to download any…
-
1) Yes, you do have redundent status, and the desire to "automatically" move things to the next column is a broken requirement. Instead of having two status that represent the same thing, ("done by developers" is the same as "ready for testers"), have one status, but use the columns as they are intended. Let's say your…
-
Project = <project name> There is no limiting in the results, it gives you a list of what you searched for. The issue navigator will show you the full list, but paginated, so you only see a cut off the top of the list.
-
Your application links will be fine with these versions, they don't change the underlying mechanisms enough to warrant deleting and re-establishing the links. The only bit that will fail is where a recent product expects one of the others to support a clever action, but the target is too old to have it. It will fail and…
-
Ok, that rules out a looped transition. So it must be a validator or post-function that is failing when you run it. Errors in those should be written into the log (whether they are shown to the users or not), so you'll want to have a look through that next.
-
There's no function for that. The closest you'll get is in those two add-ons
-
This is something you should do from outside JIRA. Your powershell script that runs every minute can interrogate JIRA over REST, asking it if there are any new requests of a certain type, and then restarting if it finds an appropriate one. I woud make it a bit more clever than just that, I would get it to update the issue…
-
I don't understand that comment. A label field makes suggestions based on pervious labels that have been entered.
-
It's not been removed. It was never there in the core product - you have to add it yourself with an add-on that provides the condition, or create a script for it.