Comments
-
You will need to get a time-machine and go back in time to when Cloud worked that way. I am sorry, that is a very unhelpful answer, it's a very short reaction based on my dislike of people throwing up video answers and then failing to take them down when they become irrelevant. The longer, but hopefully more useful answer…
-
With Scriptrunner, what did you try? I'd start from something that probably includes lines like * import com.atlassian.jira.pageobjects.project.components * issue.getComponents() * component.setLead( <user> ) But obviously, I don't know how you are choosing the user to set or where you're getting the component from.
-
Argh, I'm so sorry, I have read that Public Links does that, but it obviously has not stuck, and it did not cross my mind at all! I'm really glad you got there, and thank you for telling us what it was too!
-
I think you need to think it through from the point of view of someone who needs their page restictions to work by default and not have to rely on every single author and editor getting it right every time.
-
For system fields, it nulls them out in the database. For custom fields, it removes the line for value in the database. On the front end, both of these work the same - the field is empty, with no options selected. It doesn't set them to default.
-
That happens automatically when you upgrade, it's not something a human sets. And I'm not an Atlassian, I have no access to the systems anyway. If you've made payment, then the limit will have been increased already.
-
I think this definitely needs to go to Atlassian, I can't see why you're getting the free options only when you're paying for more.
-
You will need to raise that as a request for Atlassian support, they will change it for you (once a year at most if memory serves). Or, you can subscribe to company_name.atlassian.net as a new service, take a backup of the team one, and restore it into the new one (then dump the old one)
-
A site admin administrates the whole Cloud suite (which may well only be one system, but is usually several) A Confluence Admin can administrate Confluence. You get that by being in one of the groups named for it in the global permissions. However, I notice you have your site-admins group enabled for this, so that would be…
-
You will need to do that yourself, see https://support.atlassian.com/jira-cloud-administration/docs/configure-email-in-jira-applications/
-
Resolution, you need to set (and clear if you reopen), the resolution field.
-
Which training app is it?
-
Try the "estimation" page if you need to tell the board to estimate on story points (and hence see their sum at the top of the column in the backlog) If you just want to see them on the cards, use the dropdowns in your screenshot to select story-points.
-
For Core/Software, you can tell the handler to use a dummy or service type account when it cannot identify an active user. The email address you are configuring on the request is for the outgoing emails.
-
Ok, so Jira is more than capable of accepting data, but you need to set it up in Solman. You might have more luck asking about this in a forum that is about Solman, only a few people here might know it, generally we can only talk about the Atlassian side.
-
A project link tells you where there are docs or resources associated with the project, not a lot else. Application links enable several integration functions between services, but they're global, not at a project level.
-
You will need to ask the people who designed and built the workflow. It's something your people have done with your system, we can't tell you what they were thinking!
-
No, the layout of JSD and its knowledge base view are coded into the application, they're not configurable.
-
That's only one error that can occur, there's loads of others. Yes, it is safer to add a new table that has nothing to do with Jira, but you are now making a rod for your own back - you'll have to code a complete access layer for it, embedded in Jira's core, or including all the access layers in an app, not just…
-
You can't run SQL against Cloud Confluence, so I'm guessing you've hit the wrong tag there. This does not look like a Confluence database, and even if it were, you should not be using SQL to do anything with it. Could you explain what this has to do with Confluence (or any Atlassian system), and what you're actually trying…
-
I'm having some luck, and challenges with use UWC to migrate an old MediaWiki into confluence, so yes, people are still using these tools.
-
If it's saying "no messages in mailbox", then the email is not getting to the mailbox and you'll need to debug that.
-
No. Unlicenced users have very limited access, via their Jira account, they don't really exist in Confluence, so there's no way to tag them for watching or other things. Also, remember that they are there for access to help desk type docs, which are not generally things people would be interested in subscribing to
-
Dumping the files on a server is not going to work on its own. Whatever server you have dropped them on to needs to be presenting them over a url to the outside world, so that Jira can go read it. Forget Jira for a second, can you visit the url of the images you've uploaded in a browser?
-
I'm known for doing this with bash scripts, literally calling "curl" to send a batch of data to Jira for it to create the issue I want. If it were me, I'd simply have solman run one of my scripts. But I don't know what solman supports - it might be able to do a rest call via a dialog, it might have an internal scripting…
-
That means reading all the workflows, identifying which one you are using and parsing the xml to find the id of the transition. api/latest/workflow is the REST endpoint for working with workflow
-
Is it truly gone, or just not showing somewhere?
-
Correct. And you will need to match licences with the core Jira they are added to - number of users and type of service DC/server
-
Yep, but you do it with "email handlers" which are not a project function. You'll find them in the admin section and when you set one up, it will ask what project incoming emails should create issues in (amongst other questions)
-
No you absolutely can not "just add a column", you will break it completely. Please also have a look at the rest of my answer, it's not just breaking the move to Cloud or DC you need to worry about.