Comments
-
Start at https://developer.atlassian.com/server/jira/platform/rest-apis/
-
I'm afraid that does not really answer the question. But you still should not be reading the files from the server, they're not suitable for it. For automation of downloads of data, use the REST interface.
-
Two ways to do it: 1. Only have the transitions you need in the workflow - you could edit the workflow and remove the "all" transitions, changing it so that you only have a forward and a back in the workflow. 2. Probably more useful for the use-case I'm imagining - add "conditions" to each of the transitions that says…
-
Wendy will have set up a "resolution screen", separately to the "edit screen"
-
I have a feeling that this question is about trying to download an export directly instead of going through the UI. Please, do not bother looking in the tmp or working directories for it. The file is not always there, it's usually not complete and it is often deleted before you get to it. Jira does a lot of the work of it…
-
Resolution is not quite "mandatory" (that's a Jira-specific word used for the flag in the field configuration scheme). You can leave it blank, unlike mandatory fields. The behaviour is that when it is offered for edit, there is no "empty" option, and it defaults to a value. So it's always set if you create/edit using a…
-
You do not. A board is not a container for issues. A board is a view of a selection of issues. For an issue to appear on a board, it must be selected by the board filter. So, to get it on the board, create the issue with data such that it is selected to be on the board.
-
This should be no surprise - the plugin states it is for Jira 7, but you have forcibly installed it in 6.3. It was very unlikely to work. Remove the plugin, then you have three options * Upgrade to a version of Jira that the plugin works with * Check the plugin to see if there are older versions that do work with your…
-
You'll need to read your logs and look at the error to see what the problem is. "Java exception" only tells us "something broke", we can't diagnose anything from that.
-
Which fact?
-
It's by design. Users who have not chosen a favourite get the system dashboard because it's intended for you to use it to show them around in general. Then when they understand dashboards, they pick some favourites which suit them better. They can still select the system one as a favourite - look for "system dashboard"
-
So, not the UI, but the issue data is out of date. That would be a symptom of a broken index, yes, and a re-index should fix that. Only admin being able to log in suggests a broken user directory. I would guess that your admin is in a local directory which is working, and the others are in another directory, which is not.
-
Ok, we need to take a step back. You are saying "UI data of Jira", but I cannot work out what you mean by it. The UI is a set of dynamically built web pages served up to the users. While it is "data", it is not stored. It is built when needed. So there is nothing you can "lose" with UI data. I think we need another…
-
Do you mean the search indices? That's Admin -> Indexing -> Re-index Or do you mean the indices in the database? That's a DBA task, and depends on which database you are using.
-
I have a soft-spot for old Sci-Fi TV shows, but I've won more than one pub quiz with my totally nerdy knowledge of the stuff one chap was involved with in the 70s and 80s. If you're not a sci-fi nerd, will probably not recognise "Terry Nation", but I do think you'll recognise one of his more famous creations. This one was…
-
I'm afraid the REST API does not have a way to do this yet. Closest you can get is "current user's favourites"
-
I'm usually a little more brutal to start with. Jira can tell you what it is using and enable some easy-ish housekeeping. Go to the list of workflow schemes and delete as many of the "inactive" ones you can. Then go to the list of workflows and remove all the inactive ones there as well. That leaves you with a system where…
-
The buttons are transitions, so as we've said, you need to add a transition out of the current status and into the new one. The workflow bar is designed to try not to over-flow on the screen. When an issue has lots of outgoing transitions, it displays the first few (default setting is 2) and then shoves the rest into the…
-
What do you want from this "integration"? Without any knowledge of what that means, all I can do is point you at the docs Jira has on webhooks and its REST API
-
This is the same problem - documentation on what?
-
"Communication" is just as useful as "integrate" when describing what you want. What do you want this integration/communication to do?
-
What user directory are you using?
-
It might sometimes put things into the Tomcat working directory or temporary directories, but that is not something you need to worry about, as they're transient and not needed if Jira is stopped. A background re-index is just updating the index, it's not creating copies anywhere.
-
The app has added a small "page has been viewed" thing to the view of every page in your system. If you click on that, you will get the viewing information for the page. It's also added a tab to "space tools" for getting numbers about the whole space.
-
Quick filters do not sort the backlog, they are to narrow the view to a selection of the issues within the board. Your backlog is sorted by the board filter (which should be "rank" to allow you to change the order - it could be other things, but you will then lose the ability to order the issues)
-
What do you want from this "integration"? Without any knowledge of what that means, all I can do is point you at the docs Jira has on webhooks and its REST API
-
Those buttons are not "fields", they are transitions. Transitions change the status of issues, and are often named after the status that they will move the issue to. You need to decide what "validate" would actually do and then edit it into the workflow. For example, as Ollie suggests, the most obvious option would be that…
-
Yes, it does. To do it, you'll need to decide what you want from the integration and then find or write things to do it. I know this is a vague answer, but it's because "integrate" is a suitcase word - it does not tell us what you want, just that there is something there that could be almost anything.
-
Ok, the system fields always have searchers. Which system fields are missing? (All the system fields have a "type" that's the same as their name, so we don't need to ask about them)
-
What type of fields are they, and have they got "searchers" set on them? (Admin -> Custom fields -> <custom field> -> Edit will tell you what the searcher is. Almost all fields have one set by default)