Comments
-
Hmm, that suggests that the post-function is not giving the creation process the mandatory fields the new issue is demanding. I can see that they are set up correctly, so I'm really not sure what might be going wrong, making me suspect it might be a bug. I'd want to read the application log, but you're on Cloud, so we…
-
You probably want to associate the file types with different applications in your operating system settings.
-
That's a non-starter because fields do not belong to projects, they belong to issue types within projects. A bug in project XYZ can have a field that bugs in ABC do not. To find out if a field is present in a project, you are going to need to read the tables that hold the custom field contexts, the field configurations and…
-
The SQL answer is one way, but you *must* take a full backup before doing it, JIRA *must* be offline, and you *must* do a full locking re-index afterwards. Ideally, you should have got the date right in the import.
-
Place a condition on the workflow transition to prevent the agents seeing it.
-
Although it is wrong, as changing the date using SQL is a bad idea, and the answer neglects to mention all the things you need to do as well as the actual change.
-
What happens if you create an identical issue manually in the UI, setting only the four fields you have named in the post-function?
-
This is a query that involves a lot of joins and requires you to really thoroughly understand the JIRA database. Far too many people don't, because it's not the right way to do it. SQL is the worst possible way you can interact with JIRA data, because it has been built up as a data store, not a reporting system. The best…
-
Ok, try running the query you want in the UI, using the advanced search option so you have the plain text of the JQL you want. This can be fed straight into the REST call to run the same query.
-
As an administrator, go to Admin -> System -> audit log. Stuff in the JIRA Admin interface moves in different versions, so I'm never sure I am giving the right directions. I tend to use the search all the time - try just typing "audit" into the admin search box.
-
You've answered your own question.
-
Yes, you might run into some. Depends on your setup, data and add-ons. Try a test run, that will tell you what you need to know. Although a standard, no-add-on 6.1 to 6.3 seems to run flawlessly when I've tested it. (and 6.2 and 6.4)
-
By far the simplest option is to remove it from the create/edit screens. No messing around with flags or other settings. You just don't get to edit it any more
-
Run a filter for the issues you want, save it and subscribe to it. You'll get a basic list of issues matching the filter on a regular basis. If you are on JIRA Server, you can customise the email template that generates the content of the subscription emails.
-
Wrong version of the add-on. You should have installed the version you had before. Problem though, with an expired licence, it's not going to work.
-
First hit on my search engine returned the obvious - https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-query-issues
-
This is something you'll need to take to your JIRA administrators. It does look like they've changed something which is now breaking your calls, and you'll need them to tell you what, or fix/revert it.
-
I am sorry, I do not think this has translated well. I can not start to guess at what the title means. I do not know what a "power supply of JIRA" might be. I do understand that you are using the REST API, but I don't understand where you are going with parameters, codeclient or principle uprest I understand you are trying…
-
Have you got the admin audit log turned on? If your President is giving you bad advice, you can rely on expert advice from the ecosystem, which clearly says "keep them to an absolute minimum, or you *will* end up in a mess" (3 part-timers as a minimum, 10 as a max, for a very large organisation)
-
U:\ is a relative thing on individual clients, it may not be the same everywhere. It's also not a url, so you can't use it as a link, unless your browsers support the format file://U:\path You can however have a look at the actual mapping - it should also be exposed as a file resource, so \\server\path\file - that gets…
-
How is the link exposed to the network or internet? What is the url of the "computer's filespace"?
-
What conditions do you have on the "all" transitions into the first three status?
-
Great, thank you. That takes it down to a simple networking issue - your network is routing internal users using help.company.com to the wrong place, directly to the server instead of through the proxy. You need to get that corrected, so they hit the proxy server.
-
You'd need to rewrite the system add-on that provides the template (I'd strongly recommend creating your own instead, and turning the system one off - that way you remain supported)
-
Sorry, you've inserted two lines in there that contradict each other again. Please, could you answer the questions without adding contradictory lines. * [ok] Your base url is set to help.company.com * [ok] When people use help.company.com from outside your network * [?] When people use help.company.com from inside your…
-
Not natively. But if you either: * download the latest Server version of JIRA, install it, and go find the <home>/import/startupdatabase.xml in file * get a new Cloud account (with no data) and run a standard backup and download that Then you can use a "restore system" on your Cloud and pull it in, erasing all your bogus…
-
There are two levels of access involved here. * As an administrator, you can see the header information of all projects so that you can administrate them. * As a user, I suspect you do not have permission to see the project. Admin rights are deliberately and rightly separated out from user rights. You should be able to use…
-
That does not sound right, and contradicts what you said before a bit. I'm going to write out what I think is going wrong and I would like you to confirm or correct it. * Your base url is set to help.company.com * When people use that to access the system from outside your network, it works ok * When people use that to…
-
You need to access JIRA by it's base url. Things break if you use an unknown url, because it doesn't know where to look for things, or when it reaches out, there's nothing there.
-
Not really. An issue type is an issue type. That's it. You can stick a field on the issues for the subtype if you want, and maybe give it different contexts so you get different options by the main type. Or maybe use a behaviour (ScriptRunner add-on) to change the possible options in the list by type. Or bury it in the…