Comments
-
That suggests the system is using a different authentication method, which you'll need to replicate if you want to log into the database.
-
This usually happens when Jira can't talk to itself. Or rather, the Jira dashboard is trying to talk to the Jira back-end, it goes out over the network, but it can't get there for some reason. It manifests when you enable https often, when the certificate you're using to encrypt everything has not been installed in the…
-
No. The workflow is tied to the project and issue type. If you need an issue to follow a different workflow, you have to move it to an issue type that uses that workflow. You'll need to define different issue collectors to select different issue types.
-
No, it's not just to do with speed, although that is a factor. If you've provisioned a fast disk with NFS over it, it reduces the risk and gives you better performance, but you still should move to a supported file system. There is a very low risk of data loss. But a much greater risk of performance issues and down-time. I…
-
Workflows are not "shared with projects" directly and you can't "upload a workflow to a project", they are associated through the "workflow scheme". You create a global set of workflows (this is often automated by the project creation process), and then a set of workflow schemes that tell Jira "for this project, use this…
-
I am afraid your question lacks enough context for us to be able to help. What do you mean by "rules", and what are these "tasks"? Sub-tasks? Related issues? A process people need to do when a story happens?
-
I've always struggled with doing it with firewall routing, mostly because it's inside a complex network - chucking up a proxy and telling the network team to deal with routing is a default for me! Nicely fixed, I've added this to my bookmarks!
-
Looking forward to seeing old friends and new! For those who haven't met me, I'm English and work for Adaptavist, based out of London (I live miles away though and only go to London to physically see people a couple of times a month). I'll be mooching around Vegas for a couple of days before. My other half has always…
-
You will need to go through each permission scheme and add the group to the permission "manage watchers". Or, better, allow the right roles that permission and put the group into it.
-
Oh, well, that could explain it - the cached data persisted because Confluence was running. A restart after hacking with SQL isn't good enough, it could have made its way into disk caches and then back into the database. You should never, run SQL on a running Atlassian application, you can lose everything. In this case…
-
Could you explain what this has to do with Jira? I can't identify what part of your process is running on Jira or where you are stuck with it?
-
The only thing that might mess up the status is if you change the workflow scheme. The issue status will only be affected if the new workflow for any given issue does not contain the same status the issue is already in. Imagine you have a simple case of two workflow schemes. * Scheme 1 has one workflow with "Open -> In…
-
See https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html
-
What about the language in your profile?
-
Nothing new since the answers above.
-
They do - the date is under or next to your name.
-
Did you have Confluence shut down when you did this, and re-index it afterwards?
-
Does your colleague have "add comment" permission in the target project? I've seen that cause this a couple of times.
-
An export to Excel (well, XML that says "Hi, I'm a spreadsheet" anyway) used to be part of the core - it was removed in favour of the CSV export! A bad decision in my opinion, the CSV is (still) not ready to replace it. The Atlassian line seems to be that the CSV is good enough, and that you shouldn't really be exporting…
-
There is no group-by clause. A Jira Query Language (JQL) search returns only issues, no data, or manipulation of data. It is up to where you use it to sort, group or whatever. You'll need to find a report that supports grouping, not change the query.
-
People use the default language unless they choose to override it in their profile - go to your profile, edit it, and you should see a field for your chosen language. Spanish is one of the options.
-
You need to check each permission scheme used by each project the issues you are trying to move are in. The permission scheme is the main driver of who can and cannot use the "move" function. If you have granted yourself "move" for all the projects, then check the workflows for the blocked ones. It is possible to add a…
-
@Philipp Gerth- it's looking increasing likely to be "never" @Daniele Margaroli - correct, they only work for single-workflow projects, now that the ability to change workflows can be delegated to project admins
-
Most Unix-like systems consider ports below 1024 to be "privileged" and also known attack vectors - most cracks will attack 1-1024 because most people stick standard services on the recommended addresses (so if I have a good SSH crack, I'll try it on port 22, Whois on 43, LDAP 389, and so-on). Three options: * Run Jira as…
-
We don't know what forum you are talking about (especially as Sourcetree is not forum software)
-
No, generally. In order to do this, an App needs to have code to support itself being enabled or disabled by space. Not many of them do. Most of the theming Apps for Confluence are good examples - a space admin can select one of their themes or any of the others installed - that means when they're using a "system" theme,…
-
The "reporter" is a slightly odd permission-based setting. To be a "reporter", you need to be able to create issues in the project. This means you can limit the reporter options by changing the permission scheme. I suspect you'll find a default there already, like "all logged in users" or "all Jira users" - cut that back…
-
You still have not explained what any of this has to do with Atlassian systems. My guess is that one or more of the things you are asking about uses Confluence for a documentation system and you've found a link for "help with Confluence", rather than "help with the subject I'm stuck on"
-
Get a GC-VM, make sure it has an Operating System that runs a version of Java that supports the Atlassian software you want to run, then download and install the software you want.
-
You will need to explain this better - you've given us a fragment of a problem without any context. What do you specifically mean by bug/defect tracking? This means different things to different people. If you need an issue type of "bug", either select a project type that has it by default when you create it, or add the…