Comments
-
One quick thought to rule out - could it be their email client? Some will automatically drop extraneous spacing when rendering mail (usually, that's done for multiple spaces in html - renderers will take 2 or more spaces to mean 2 spaces max, but some do it for extra line feeds/carriage returns as well) To test that, send…
-
Your "create account from helpdesk" process is incorrectly creating Jira users, not customers. You have not told us what you are doing when you "create account from helpdesk", so I don't know what to tell you to look at.
-
Not natively, but there are admin apps that can help, or you could look to scripting apps.
-
Are the accounts all internal accounts? Or are they external, from LDAP or some other directory?
-
I'm afraid we're a community of people here to talk Atlassian. We have less access to, or knowledge of, your Atlassian Cloud site than you do. You'll need to ask your colleagues or co-workers, or the people who asked you to use it in the first place. Someone in your organisation must know who the admins are. If you remain…
-
Projects do not have backlogs. Backlogs are a part of boards. Boards are not containers for issues, they are a view of a selection of issues. (It is common to set up "board = project" on a simple 1:1 basis, but it's not universal) If an issue is in a backlog and you think it shouldn't be, then there's something wrong with…
-
Yes, that's correct, the key of an issue is the key of the project it is in and the sequence, separated by a hyphen. To be clear - these are not "tags", they are the unique human identifier for an issue. If you want to use a different identifier for the project part of it, you will need to move the issues into a different…
-
Removing lines from this tables destroys some of your issue data, so that should not be done. (Plus you'll need to be doing related deletes, the table has relationships with a number of other things and you need to be really careful not to end up with an unusable Jira due to data corruption) Partitioning is not supported…
-
This simply means whatever database you set up was ok during installation, but is now no longer available to Jira. Either the database service has stopped, it's not available on your network any more, or you've reconfigured Jira to look at the wrong thing. Without knowing exactly how you did this new installation, there's…
-
What do you want from a "suggestion"? I'd tell the integrity checker to fix your broken data. That's what it's for!
-
The impact is that it fixes inconsistencies in your data, correcting some reporting and allowing some stuff that was crashing before because of the inconsistencies. I don't think that's really what you are asking though, could you explain a bit more please?
-
How did you try to do this "migration"?
-
But now you're into describing a role, not a job. I'd definitely argue that improvements have a far wider scope than you had in your bullet points, and I don't believe an Atlassian admin's role would exclude training, there's always people who need some. I just don't want people landing here to mix up the role with a job…
-
There is no implementation of a multi-level cascading select I can find as a Cloud app.
-
There's no easy way to see it (it changes roughly every six weeks and doesn't tell you anything about compatibility, so it's generally useless to most people and so Atlassian don't make it easy). The place we've always been able to (reliably) find it is as a result of a rest call - see…
-
There's no way to wedge a Jira Service Management portal in front of a Jira Software project. While the data is broadly compatible or at least ignorable, the purposes for which the project types are for are not. As an example you simply can't do Scrum while under an SLA and you can't measure Scrum or Kanban in a way that…
-
It's been archived and protected, as Atlassian don't want anyone being mislead into thinking they should be using Jira 3
-
In fact, SQL queries won't get you anything more useful - the project and custom field creation dates are not recorded in the database against the items themselves. Any SQL you run would only be able to find the data in the audit log!
-
Ok, well, it redirect me there too, but then takes me to a "you do not have access to this system". You must have been added by the system owners, and I'd find it very odd if they'd just added you without a request from yourself. Maybe check the "people" list to see if there's anyone you recognise to ask why you've been…
-
If you don't want a "connector", then you are stuck, you're explicitly ruling out connecting to it. Broadly, your options (all of which can be described as a "connector") are: * Use an app that understands Cloud Jira and Powerbi, enabling them to talk to each other * Get Powerbi to use REST calls into Cloud directly to…
-
It's never going to reach your "return 0". The line above it already returns from the script no matter what, so it's stopping there.
-
Ok, a 408 is a timeout, which implies there is something there, but it's not responding to anything after the initial "yep, give me a sec to get some data for you" that a page sends back to your browser when first contacted (you'd get a 404 if there was no response to the first contact) The thing that is running there will…
-
I set the permissions so that only a small group of people can create spaces in Confluence, and ensure we only have 3-10 trained Jira admins who can create projects, and turn off "create team managed projects" in Cloud Jira, or at least limit it to the people you trust not to make a mess. Your problem doesn't sound like…
-
There's a lot in the "and more" section though ;-). Apps, training, improvement, support, etc.
-
What type of field is 11588 ?
-
The transition used to move from one step (status) to another is not recorded by Jira, only the change of status is logged, and there is nothing to work with that you could infer it from either. So there's no way to search for it, even with Scriptrunner. SR is powerful, but it can't do anything with data that simply isn't…
-
We cannot begin to help you without at least a description of "having trouble". For all we know, it might be an angry penguin jumping on your keyboard every time you head for the "upload" button. If you want help with a problem from people, you do need to begin to explain what the problem actually is.
-
Create the three pages Example1, Example2 and Example3 as normal. Now create "All information", and instead of body text, use the include macro, such that the body of the page is just {include: Eample1} {include: Example2} (include: Example3} This will render all three pages as though they were on one page. Edit an example…
-
It sounds like your helpdesk is creating Jira user accounts, not customers. When you say "create account from the helpdesk", where are they doing this? What is the process?
-
That's something for your organisation to decide. You'll find it varies by product, team, customer and so-on.