Comments
-
No. Even if you hacked the macro code a bit, so that download disappeared, you can't stop someone downloading the file, as the data has to go to them for them to view it (or even if you got clever and streamed it, it's very easy to grab a stream)
-
Ok, so the next question - what do you mean by "integrate"? It's a good suitcase word for "I want things to work together", but tells us nothing useful about what you actually want them to do with each other. Jira has a REST API for other systems to talk to (both read and write), and extension points to allow you to add…
-
It's often in the footer, but not always. It is always shown in the help menu. Please check "about" in the help menu, as I suggested earlier.
-
I don't think it's Atlassian being intolerant - showing support for some people who regularly suffer intolerance is not intolerant itself, it's the other side of "tolerant"
-
Often the footer has the answer, but the best place to look (without admin access) is simply in Help -> About (the menu in the ? icon on the top bar, or at the bottom left if you're on Cloud)
-
I am afraid you need to do some diagnostic work before you can do a lot about this. You need to know what is causing the slowness (CPU, Disk, Memory, Network, or something else) before you can fix it. For example, there's no point in increasing CPU power if the disk speed or network are the problem. There is no way to know…
-
I'm afraid you've reached the wrong place. This is a community of end-users of Atlassian software. We're happy to help in general, but we are not your administrators. You'll need to contact your Confluence admins - there may be a link in the footer for "contact admins", but if not, you'll need to search your Confluence for…
-
There is no official way to turn this change off, but see https://community.atlassian.com/t5/Sourcetree-discussions/The-way-to-change-icon-for-Sourcetree-app/td-p/1110914 for a technical workaround for it.
-
It was me. Part of your posting was offensive to some people here (including myself) and likely to attract unwelcome and noisy comments. I removed the parts that people might find offensive, and left in the informative useful parts. I do not believe you intended to be deliberately offensive. But there are people here less…
-
What do you mean by "default"? Are they automatically added to new spaces? Or do you mean you just want to get rid of a load of groups and people?
-
There are many factors that can affect upload and download speeds, and there's not a lot of point in talking about all of them in any detail until you know where the problem is for you. What you need to do is pretty simple at first - monitor it while running a large upload and then again during a download. It is quite…
-
This can't be done. A board is not a container for issues, it is a view of a selection of them. A project is a container for issues, and when you create an issue it goes into a project. You can't decide to put an issue "in a board or a project" - an issue is always in a project (although you can move them), and a board…
-
Note that if an index run fixed the problem, all it has done is fixed the data. Whatever is causing the index to go wrong should be investigated and fixed. I would start with a good look at the history of ABAIT-9946 - look for the change of status from <something> to Development. Then look at the workflow for the…
-
My guess is that you need to ask your administrators about this. We're a community of end-users of Atlassian software, not the people running your system. Also, this does not look like an Atlassian system - "smart TP id" and "Scheme" are not things that mean anything to an Atlassian log in.
-
I'm not sure what you disagree with. A sub-task is part of an issue, and an issue lives in a project? That's how it is, so there's nothing to "disagree" with there. It's total nonsense to have a sub-task in a different project, they're part of the issue.
-
It depends very much on what the data is for and what you are doing on it. A good principle when trying to design or improve a Jira setup is to work backwards. Essentially, you are putting data into something so you can track things and see progress. The end result, no matter how you do it is "reporting". What do your…
-
Go to the project, look at the configuration of it, you will find a "fields" section which refers to the field configuration and field configuration schemes.
-
Well, you can "use the same issue number in another sprint", but that means "using the same issue in the same sprint" - not re-using it, but taking the same issue into another sprint. The whole point of a unique issue number is that it is unique!
-
Issue types (including sub-tasks) have "screen schemes" which tell them which screens are to be presented to people when they are viewing, creating or editing them. Your project is configured for a mandatory due date for the sub-tasks, but the field is not on the create screen. Your admins have two options: * Make the…
-
No. Some people try to use Confluence (or even Jira attachments), but these are not suitable for large trackable objects. Generally, most of us use a build server to publish builds into software designed to be a repository - artifactory for example.
-
That is not a menu, it is a field. You add / change / remove Options in custom fields by going to admin -> custom fields -> <this field> -> Configure
-
Absolutely correct (and you can't do it on server either - there used to be bugs and hacks that let you create duplicates, but they break everything, horribly. Fortunately mostly fixed now) Cloning may be their best option, as you suggest.
-
How did you "create a drop down menu"?
-
You'll need to explain what EVS and Unitask are - most of us don't know.
-
Depends on which menu you mean?
-
We can't help you with that, we're a community of end-users of Atlassian software. You'll need to talk to your Jira admins. If you don't know who they are, you will have to ask other users (or the person who gave you your access)
-
Please check the permission scheme to see who has delete permissions.
-
The logo is a temporary promotional thing you can and should completely ignore, it'll change soon without you needing to do anything. Annoyingly, you can't change it yourself.
-
The logo is a temporary promotional thing you can and should completely ignore, it'll change soon without you needing to make any changes. I am very worried about how it got "uninstalled" though - Sourcetree won't do that itself.
-
Yeah, scripted fields have to be done in two steps - part of it is done in Jira, the rest in Scriptrunner. The Jira part is the field definition, like any other custom field. Add a custom field of type "scripted" to your Jira and put it on the issue view screen(s) you want to see it in. Edit the field definition (not…