Comments
-
No, you'll need to do all the work of conversion by hand, translating the bits you think you want. Jira's REST API respects the permissions within the system, there's no need to block API access by user - all you have to do to stop them using admin functions over REST is not give them Admin rights in the application. There…
-
We can't run translation tools over the messages in images. Could you show us the errors in English?
-
What error? You have not given us anything to look at here.
-
I am not sure what you are trying to do here. You have said you want to exclude some status for a queue, but then given us two queries. Which is it?
-
@Lauren Black thank you. That's a way better answer than I could give, and I would love to hear more about Engage 4 Good.
-
It appears that you've given a dummy account to Atlassian, so they can't contact you. 100% kudos for security and anonymity, but 0% for being able to get it fixed, because your identity is necessary for working out your rights over the account. You'll need to log in with an identifiable account that has system access. I…
-
It would be a better question to ask for "open in new tab when it is appropriate and not going to confuse the user" One of the biggest UI complaints I run into nowadays is "I have too many tabs in my browser". Just stop inflicting that on people. It's ok (but not great) to open a new tab when you click on something that…
-
You can calculate by project, board or, with a bit of fiddling, almost anything else you want to. Boards are however easiest - Scrum boards give you a velocity (so you can easily see how much the team can take into the next sprint) and Kanban give you a throughput, so you can see how much the team is getting done regularly.
-
Because it's about working for people, I'd be tempted to move this to the "jobs" section, but I think it's actually better here. It's a good place to talk about charitable work, and your offer to help out is fantastic. So not in the wrong place at all!
-
Ah, sorry, I misunderstood the question. What version of Jira Service Management are you on? The ability for customers to configure their view of a portal is relatively recent, so if you're on an older version of it, it might be simply not there!
-
No, it's not possible to hide it (reliably). Changing the configuration of the fields won't hide it, but it will stop your problem of "lets people bypass mandatory fields", which means there's no reason to try to hide the button.
-
Yep, most use the same principle - a project to handle things you don't know where they land and then a new issue in the right place when you've worked out which area(s) need to work on it.
-
Ok, so you're using the wrong url - your script is not a browser, so it's not got all the functions you need to use a direct download. You need to swap to using the REST api.
-
I saw that discussion because someone pinged me about it. They said it felt hostile and accusatory, rather than inviting discussion (or questions), a rant by someone who hasn't bothered to engage before, or worse, is someone who has, and has created a sock-puppet account so their vitriol doesn't get associated with their…
-
Moving the column to the left of the "done" column will fix all your problems effortlessly. It won't even change any data on your issues.
-
I'm with you on this Team-managed projects have a very very long way to go before they could replace company managed projects. They need to implement cross-project working, shared fields, common workflows, shared permissions, and and and. Probably most importantly, they'd have to remove the ability for teams to configure…
-
Welcome to the Atlassian Community! There's no such thing as "in" with "and". It's logical nonsense because there's no way to explain it to the system you want to ask it of. The closest you could get is "has all of these attributes", but no-one usually bothers to implement that because you can do it quite clearly with "x =…
-
This is an odd one - the UI does not allow you to have projects with no notification scheme. Even if you delete an active one, associated with a project (which it tries to stop you doing), it'll set it back to "default". But, yes, if you do somehow end up with a project with no notification scheme, then yes, it'll warn you…
-
You don't get direct access to the database on Cloud, so there is no direct answer to this question. You could do it on Server, but you would be making a nightmare for yourself, no-one should be looking at using a Jira database for anything other than running Jira. But it's worth a look at the source of the question. What…
-
There's a fundamental question of why are you creating customer bugs in the wrong place? But when you're in a place where the people creating issues don't know where they should be added, there's a standard approach - use a helpdesk style project. Customers can raise everything in one place, and the agents who "triage" the…
-
Yes, the "move" option is complex. It has to be. By changing an issue to a type with a different configuration, you are effectively making a structural change, and that process may need to ask for new data or warn you that data is going to be deleted. In the case of converting Story-level issues to Epics, or vice versa,…
-
So we can't answer the question for you. What do you want to be the trigger for your issue creation?
-
Welcome to the Atlassian Community! Your quick filter is probably just "issuetype in subTaskTypes() and estimate > 0" But there's a few problems with what I think you're doing, which you'll need to fix before your filter can be of any use. Are you putting sprint estimates on sub-tasks?
-
No, you won't be able to create a new project with a used key. Jira keeps a record of keys in order to preserve the issue histories.
-
It is the different configuration. You can use the "move" option to change the issue type, it will take you through a process of checking for data loss and filling in required fields.
-
It's there for letting the issue create code put a value into the issue. You don't really have any other option than putting the value into a custom field if you want to keep a record of it. You can not set an issue key in Jira, only Jira can.
-
Welcome to the Atlassian Community! Oddly, the first hit on every search engine is https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-servicedesk/#api-rest-servicedeskapi-servicedesk-servicedeskid-queue-queueid-issue-get
-
Welcome to the Atlassian Community! This isn't an Atlassian problem, you'll need to talk to the Azure Data Factory people about why you can't get it to read your Jira database. All we can suggest is that you look at the settings, are you sure the connection is properly configured?
-
In a Scrum board, the issues are supposed to be visible during the sprint (they have to be, otherwise you can't report on them. You say "post completion" though, which suggests what you really mean is that the issues are moving to the next sprint. When the sprint is ended. are the issues in the last column on the board?…
-
Start at https://developer.atlassian.com/server/jira/platform/rest-apis/