Comments
-
You will need to contact the administrators of the Jira system your people are asking for access to. Here, we are a community of end-users of Atlassian stuff. Your users appear to be asking for access to one of your internal systems that we have less access to than you do! The ggayathi you see on Atlassian websites is from…
-
You could try the built-in custom field for "projects"
-
If your board is not configured to exclude it, you will see it on the active sprint board under the issue it belongs to. Check your filters do not exclude sub-tasks.
-
As I said, yes, all for 5 agents (doesn't actually matter - 1 agent to the max would work the same) You cannot use your own dns for Cloud (yet), as I said. Yes, you can do reports. "Exporting" them is a right pain though if you want anything more than screen shots.
-
No, we need to to see the filter that the board is using. Boards are not containers or holders for issues, they work by selecting a set of issues out of the projects. The selection is what we need to look at. Go to the board, then the configuration of it, and on the main (general) tab, you should see a filter name and…
-
Off the top of my head, I think you want comment.getAuthor().getName() for the user's login (get.fullName() for their display name if you need that too)
-
It was reported, but closed as the current behaviour is the intended behaviour.
-
We know as much as you do - neither of those are acronyms I'd associate with Atlassian stuff. What makes you think they are Atlassian terms? Could you explain where you are seeing them?
-
Component is an array of 0 to many components, so I think you need to use a "contains" rather than "=="
-
Component is an array of 0 to many components, I think you need to use a "contains" rather than "=="
-
* Yes, 5 agents will enable unlimted customers, locked down to their organisations or just own requests if you need it. * No, you have to use Jira's domain * Yes, if different customers use different portals * Depends on what you mean by "export" - probably better to question why you think you want to export them * No,…
-
As mentioned above - to edit an issue, you need edit permission.
-
It's impossible to say without seeing what you're injecting and how you've tried to make it work. Have you tried to deal with all 9 places you might have to "enumerate" your field, or are you only trying to deal with the 4 main places you need to do it? (I should also point out that I'm not a Javascript coder - I don't use…
-
there should be no real difference. When you click edit > update, it's just a different way of calling the same functions that a script calls. My best guess is that the app you're using (power database fields pro) is doing something on the front-end with the UI, as well as updating on the back-end. Scripts do not go…
-
"Have a Gorilla?" "No thanks, I'm trying to give them up."
-
In theory, you can go straight from Jira 7.0 to 7.13. If you have a plain Jira with only Atlassian Applications and Apps, then I would have quite a high confidence that this will work. If you've got lots of Apps installed, then less so, but it should still work. As always, the key is to test the upgrade first. I would…
-
Run a search (magnifying glass to the left) and make sure it returns at least one issue. In Cloud, the "tools" menu is always there at the top right, as a ... icon, as long as you have the right permissions to do at least one thing on it.
-
This is the screen used by the workflow to ask the users for a resolution when they're closing an issue. You can remove it IF you have decided to set the resolution some other way when closing issues in that project.
-
One thing that is indirectly related to volume of projects is permissions. Every time someone *might* want to do something, Jira does a permission check. These can be quite complex if you've got complex permissions. Simplify them where you can - share standardised schemes, and most importantly, use roles. If you can,…
-
If someone can log in, they take a licence. As Prakhar says, your admins have to log in in order to be able to do the job.
-
It's your operating system that is struggling to open the directory, you need to use a file browser that can cope with the name properly. Older backups didn't have it because they simply didn't need it. The latest version has a use for it.
-
Are you a project administrator on ALL projects named in the board filter?
-
My guess is that you have installed Jira on a server and accepted the default base url of "localhost" (This is a default to get you started on that server, not exposed to the outside world). You are now trying to connect as a client from your machine, and you've put in "localhost". Localhost always means "this machine",…
-
I think you need to go back to thinking about what you're actually trying to find out about the issues. I don't see that "you might be able to do some of this list of things with a sub-set of this pile of issues" is a lot of use compared with "for each issue, here is a list of exactly what is currently possible" I do have…
-
You need to make sure you have "bulk edit" permission in the global permissions. That's the only thing that controls whether it appears in the tools menu or not.
-
Not at present, no.
-
On a Linux machine? I think your question needs to be explained in more detail. What are you trying to do?
-
It's not in the slightest bit "contrived", it's a real example from a simple Jira. If you want to look into it more, consider the lines with more data: * 120: Open -> In Progress * 120: Open -> In Progress * 120: Open -> In Progress Please tell me which one of these I need for my issue? The point here is not about…
-
That call will list everything on the board. So you will need to look at why the issues are, or are not, on the board.
-
There does not appear to be a problem with this. You'll be able to restore from it fine. Could you explain the concern in full?