Comments
-
It is! Note that it is an "edit" - it will change both your Jira and Confluence on that url, you can't leave one behind.
-
Are you 100% sure that the workflow conditions allow you to resolve the issue from the status it is in in the first screenshot? What do the conditions on the workflow transition you are trying to use say? After checking the workflow (and I'm repeating it because your reply does not convince me you have, and 99.9% of these…
-
Because you are not set up as a "customer"? I'm afraid there's not much in your question to work with here, I can't tell you a lot.
-
My guess is that the main problem is your "then edits issue type". You cannot "edit" the issue type, you mostly have to move the issue from one type to another. If you do not use "move", you can throw the issue into an unusable state because you are not updating the configuration of it. I say mostly because there is an…
-
"Burn" is about the points you have completed, not the points you have in to-do or in-progress. Jira recognises completed points with a very simple criteria - the issue/story/item is in the right-hand column on the board. It does not care what the name of the current status or the column is, "done" is just the last column…
-
I don't think there's much more you can do! Although you could try asking Atlassian to check where the extra two accounts have been used (in non-Community places) to see if they might mean anything to you, or to check if they have email aliases you might recognise.
-
There is no relationship between component and group. If you want to create one, you will need to use scripting and automation to set up the "correspondence" you want.
-
We can't see all your data, we are end-users of Atlassian stuff with no access to your system. However, can you show us the issues for the sprint on the board? What issues are in the right hand column?
-
You used to have to buy the new one and migrate, but now you can raise a request with Atlassian support and they will move the site for you.
-
You don't have the permission to use the "resolve issue" transition, or the transition does not exist out of the current status of the first issue. Check where each issue is in the workflow and what the workflow says for who can use transtions out of the current status.
-
Lupins are indeed flowers. There's a whole Monty Python sketch about them if you're into that sort of humour.
-
No, it has to use the new url because that's where you've moved Jira to. In theory, you might be able to leave a server running, serving up the old urls and rewriting them, but because an issue collector is posting data as a one-off, I am not sure that will work.
-
Each account has a unique email address that was used to create it (or has been changed to it). I'd try a password reset on the ones that are not you to see if you get anything on another address or alias
-
No, you would need to write your own code to provide such a conversion.
-
The short answer is "you can't". But that's because the REST API responses are JSON. If you're happy to write something to convert JSON down to CSV, then yes, you can get ID, labels, component, summary, versions, status, links and a load of other stuff, including the history. I am not sure what you mean by "temporal"…
-
You'll need to use Jira webhooks to poke data into CIM, or possibly email, whichever it supports for this sort of thing. Then in CIM, ask it to make REST calls or reply with emails that Jira can process (note for emails, you are going to need advanced email handler apps)
-
I'd say they change rarely - one of my Cloud clients set up with that page quite a while ago (I remember Winter/Spring last year) and have not needed to amend anything.
-
It's over at https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domains-744721662.html
-
To use it, you need * "bulk edit" global permission * "move" in the source project * "create" in the target project To do it * Go to "search" and run a simple search for "Project = <source>" * Look for "tools" at the top right and select bulk edit * Use it, selecting "move" - it will walk you through the process of…
-
Next-gen projects are a function of Jira Software. Once they are mature for Software, we may see them in Service Desk or Core, but I do not know if that is on the roadmap yet.
-
I think you have created a "next gen" project - these are simplified as Atlassian are rewriting them from the ground up, and there's a lot of stuff not yet re-implemented in them. You cannot yet flip a project back, you'd need to create a new "classic" project and then bulk-move all the issues into it.
-
I can't work out a way to do that to Jira without using apps to provide a second attachment area somehow. Are the contents of the two panels different?
-
There's an unpleasant annoyance in Jira here in that while we're told "assume the sub-task stays with its parent, as it's supposed to", Jira does not actually track it like that. Similarly to the epic-link on the parent, the sub-task sprint is not carried down by Jira. I fix this on Server by using Scriptrunner to…
-
All questions are equally weighted, the complexity of a question and the number of right answers you're asked to identify are not relevant. For a question with a "select x", we were told the question should always tell you how many answers are needed (if it was more than one) so that you're not second-guessing. Those…
-
What Test Management App are you using? Source and Target (if they have different names)
-
Burndown (and burn up, and just generally done) are very simple in Jira Software - the issue must be in the right-hand column of the board to be considered "done"
-
* My understanding is that Atlassian have a couple of bugs filed and are working on them, but have no ETA * <your choice>.atlassian.net * It's usually network latency between your site and the servers that Confluence is running on * You'll need to give us more detail on that one * Atlassian charge monthly or annually, but…
-
We're a community of end-users of the Atlassian software suites, we are (mostly) not your administrators and know less about your systems than you do. You will need to contact whomever is behind your Eudralink and/or EMA Service desks. I'm afraid we can't tell you who they might be. Your best option, if you can't find docs…
-
Does your account have "schedule issues" permission? Also, could you try the "field finder" under the "configure fields" option on screen?
-
"Completed" in Jira Software means "issues in the right hand column of the board ". You can't change that. You can change what the estimates are done on - story points, estimates or any numeric custom field can be used (with the caveat that they're not for sub-tasks, so Jira will ignore them)