Comments
-
Yes and no. I'm saying that there is no need to restrict users, you should be talking about what you allow them to do. And yes, it's complex and painful to do this by project. If you're worried about users seeing each other, you currently have to turn off "browse users" as a global option.
-
Again, your code is fetching an arbitrary version number which is not a valid entry for the field. That will not work, you cannot randomly add things to fields like that.
-
You rename it to something else. Or delete it (and tell Jira what other types to swap the existing tasks to)
-
I don't think you understand what the problem is. There's no security breach, just something that's painful to implement and not a lot of use to most people.
-
Log in as an admin and go to Admin -> Issues -> Custom fields. Find the field in there. If you can NOT find it in there, then it is not a field and hence cannot be used in searches. If you do find it, click on "edit" and check what the "searcher" is for it. If there is no searcher, then select one, and re-index your Jira,…
-
Ok, so you need to search for the field development, not development[commits].all - that is not a valid field and is hence no use in JQL
-
Nope, you can leave them in "ready for acceptance" or the three green ones. That's what boards are for - representing the workflow in a way that suits each particular team. When your developers do a sprint report, they'll see those issues as done. When the sprint is closed, the done issues don't change. When the testers…
-
Ah, thank you, that clears up what I'd missed. When you said "request", I was thinking "the way you landed in this place - a url with something mentioning 'development' in it". You meant "request" as in "a Jira issue". I should have seen that! You say there is a development field in the request/task. Can you tell us what…
-
Not directly, as "group assignee" invariably causes ownership problems within the team. The assignee should be the one single person with the ownership of the issue (even if it's only to re-assign it to someone else). But, naming a group a generally responsible as well as the single owner is good - create a custom field…
-
I usually use workflow-properties to do this. You can edit the workflow and identify the status where you want to block logging work, then add a flag that says "no one has permission to log work while issue is in this status"
-
I think it could - as your developer sprints would close on "waiting for acceptance", (and fails/re-opens could go back into the backlog), and your tester/user sprints would be separated out. The sprint reports work off the "done" column, and this scheme works for quite a few places I've seen. As long as you can get your…
-
Well, no, because I don't think it's a field.
-
I am sorry, but I do not understand that "in the request itself". What request? Do you genuinely have a field called "development[commits].all" or not? I suspect you do not, and "development[commits].all" is an attempt to run a function which JQL does not do.
-
I don't think those are "fields", so you're going to struggle to do a field based search on these. I suspect a macro could look through the content, find "open points" and drag out the next line.
-
As a general rule, put as little as possible in the DMZ. Your Confluence server has no need to be in the DMZ if there is a proxy in the DMZ that can reach into your internal network to do the proxying of the applications.
-
Yes. Assuming you have a default Jira, you already have an issue type called task, and it's a parent level one. You will need to rename that to something else, then you will be able to create "task" as a sub-task type and use it beneath Stories.
-
Do you really have a numeric field called "development[commits].all"? My instinct is that you are mistaking JQL for SQL, and it looks like you are trying to run code or a function for a development field, which is nonsense in JQL.
-
Best you can do in plain Jira is give the fields different contexts under admin -> issues -> custom fields. You might end up with the same list of options, but you can set different defaults in each context. To do it on-screen for users browsing, get Script Runner and use a Behaviour (you could try to inject your own…
-
Confluence is a wiki, not an issue tracker, and hence does not have "fields", just pages full of content. A macro might help you, but you'll need to explain how you are recording the features in Confluence and creating the "open points" field. I'd strongly recommend upgrading to a supported Confluence as well (CQL was…
-
This happens in three ways 1. Jira is trying to "help", narrowing the list down by what you have selected in project or issue type. Clear those two out for the full list 2. The fields you want do not have "searchers". Unusual, but useful sometimes. You can not search these fields because your admins have chosen to stop…
-
The best way to grant access seems a little more complex than you would think, but it gives you huge power and flexibility. There are two layers: Project Roles: Tell you who is in what role in a project (e.g. Nic is a developer and an admin, Alice is a product owner, Bob a developer and Chuck a developer and a tester. Then…
-
No, Jira does not have sub-tasks of sub-tasks.
-
You don't need settings to find this out. Open a search page as normal, and swap it into "basic" mode. It now has a handful of standard fields to get you started, but also a drop-down to the right that lists all available fields. Have a read through that, note the fields you need, then swap back to "advanced" mode (I…
-
Yes, use the standard link format to add it (Start typing a [ )
-
The cleanest option would be to duplicate the project on both Jira systems and use one of the synchronisation add-ons to send the data over to each (Look for Backbone or Exalate in the marketplace) If you want to do it exactly as you describe, you'll need to come up with two workflows with holes in them (they will both…
-
Global permissions, as I already said, If you don't have access to that, then you do not have the admin rights needed. Contact your administrators.
-
Make sure the Jira Toolkit is installed, then add a "participants" field and use that instead of assignee. It aggregates reporter, assignee and anyone who has commented into a field.
-
As an admin, check the global permissions. A user must be an admin, or in a group named in the "can create space" permission. If they meet one of those two, then there is "create space" under the spaces menu.
-
Go to the field setup under admin -> custom fields, configure the field, and remove the default.
-
You are looking at a different workflow to the one that is in use on that issue, or the status that you see on the issue are not included in the area of your screenshot. I suspect the first one of these.