Comments
-
>if its possible to create the Customers automatically without knowing them. As long as you have contact details for customers (i.e. an email address), then yes, you can add them. I don't know how to do it "automatically", but I'd reach for something in segment that can tell Jira to create new customers via the REST…
-
Go to issue search and put in a search for the ones you are interested in. That will give you a list, which I would guess you want to summarise. To do that, save the search as a filter with a useful name, then go to your dashboard and add gadgets that use it. For the case you describe a simple "filter statistics" one…
-
Get in touch with Atlassian as a matter of urgency - dead Cloud systems are deleted after 7 days of inactivity. Go via https://support.atlassian.com/contact and give them as much information as you can - most important is the url of your Cloud site, but ideally the name of any admins you might have had. If you do have…
-
There's a problem here - Atlassian already have that. You go to a shared filter, you get the JQL for it, and you can then save it or modify and save it for yourself. In every version of Jira from Server 4.0 to 7.7 and all incarnations of Cloud, going to a saved filter displays either the simplified selections or the…
-
I don't think that has anything to do with using an old licence for Jira. But https://confluence.atlassian.com/adminjiraserver073/connecting-jira-applications-to-mysql-861253043.html does not seem complex to me.
-
I think you are in the wrong place, we're a community of Atlassian users, and I don't think you are talking about an Atlassian application. If you are, then can you tell us which one and what the problem with it is?
-
No, it's because Software provides a gadget for its boards, and Core does not.
-
It isn't an issue at all. See the conversation above.
-
Tempo doesn't have this function yet.
-
The business boards are not Agile boards. Jira Software provides a gadget for Software boards.
-
There's no question here.
-
Ok, the UPM is broken then. What does the log say when you try to visit the page?
-
I think you have bought Jira Server licences, which are no good for buying Cloud (something.atlassian.net) services. On Cloud, you never get to the licence pages, it's all done behind-the-scenes for you. You log into the my.atlassian.com account that you want to buy the Cloud system with and provide payment info, and the…
-
Ohh, that's annoying, the document neglects to mention you need to have the Jira Suite Utilities add-on (or something similar) installed. Do you have any workflow add-ons installed at all?
-
Ok, just to rule it out, could you add a single line of "exit" to the top of that script, then try a delete issue again? (Remove the line after this test, of course)
-
Your "hive" pull will need to read and understand the responses from Jira then. Not really sure why you're pulling Jira data into a thermostat/home-control system, but it's good for you, why not! Time in status and time spent on an issue are two very different metrics. Simple example - the last script I wrote for a client…
-
Good question, I see your logic. But no. Default values only appear when you are creating a new issue. You wouldn't want Jira defaulting a field you have deliberately left blank every time you want to edit it.
-
If you use the calls to the API to ask Jira questions, it will return data. You will need to read that data, it will contain the issue history. This is a vague guide to what you can do. This was deliberate, because we don't actually know what you want to do with it. Given "Extract Jira issue history", we can't really tell…
-
There is no explicit "read only", but you can do it manually. For Jira, create a permission scheme that only allows "browse" permission. Apply it to all projects. For Confluence, work through each space, removing all the permissions to do anything other than read
-
On the issue view, Jira hides empty custom fields, as they're useless clutter (although, since in-line editing arrived, the "useless" part is not strictly true. Atlassian and I still agree that putting empty fields on screen is clutter, but I would like to see an easy way to get to them without having to edit the whole…
-
In a simple filter, your custom fields will be available on the drop-down list to the right. In an advanced view, start typing the name as part of a clause, and the autocomplete should help you.
-
Why are you restarting it? You can usually leave Jira running on servers for months. The last time I restarted the one at home was because I upgraded after it had been running for 7 months.
-
Why are you restarting it?
-
Use roles. Create a permission scheme that says things like * Browse: Role (users) * Create: Role (users) * Admin: Role (project admin) * Edit: Role (users) * Log work: Role (developers) * And so-on. Then, in each project, add the right groups to the roles.
-
I edited that to the url for 2018, so it won't mislead again (until the next change!)
-
Where are you trying to do this ordering? Status generally doesn't have any order, as when status matters, it's usually in isolation.
-
No. Changing the issue type is not a field change. The issue type is a structural thing, that the whole configuration hangs off. You can't edit it directly (unless the configuration for both source and target types are identical for fields and workflow), and you can't change it as a transition. You have to use "move" You…
-
It's a four year old posting, things have moved on. For support now, go to https://support.atlassian.com/contact
-
That would bias the display in ways the UI designers have vetoed. If you need it bigger, try using ctrl+ on the browser.
-
What do you mean "automatic" installation? Installations ask for a licence. As long as the version is valid for the licence, it'll accept it.