Comments
-
Use indicative names, and/or set up your categories in a structured way.For extra project level fields, have a look at the "Profields" addon.
-
No, a project can only belong to one category.
-
This can happen for all sorts of reason, but the usual one is some form of networking issue. Are you behind a firewall or proxy that could be allowing only partial access or changing the headers? (I recently broke a system by using a mis-configured proxy that dropped some of the request headers)
-
Driving it from the boards is not really possible because it's a bit of a cack-handed approach - everything in Jira runs off "find me an issue", not reports.The closest you'll get without code is what Doug says - find all the filters you are interested in, and use "filter in" to combine them. That's better than building a…
-
That's kind of a recursive query. A board is built on a query, so "jql to filter issues on a board" really resolves back to "run the filter the board is already using" The filters on boards are all saved filters - you should simply be able to find (and hence run them) from the list of all filters available. Or go to a…
-
I used the auto-transition listener in the "Jira Toolkit"
-
Not really. You create an issue, it has to go to one status. I suspect this is because it's immensely complicated to have floating targets in workflows, it's far easier to stick to something basic and clear and then build on that. There is a basic way to work through this - first, make your workflow have transitions from…
-
Asked also at https://answers.atlassian.com/questions/24281120/opening-edit-screen-is-changing-resolution and probably a different answer, as you've ruled out the screen!
-
Remove the "resolution" field from the "edit" screen. The problem here is that if you have the field on an edit screen, JIRA will set it to something. There is no option to leave it empty or set it to none, and you can't add one. Any value in the resolution field means the issue is resolved and hence, struck out. You…
-
That's part of the problem - the second user field is completely separate from the assignee. You need filters like : "assignee = currentUser() or coassignee = currentUser()", and the built in reporting and filters wouldn't see it either because they are all based purely on assignee. I find a lot of places that need…
-
You could try having a second assigned field. User picker so it wouldn't have the functionality of the single assignee, although you could still use it in workflow functions, permission and notification schemes. You could also try something funky with workflows if it is just a case of "two people must flag this as…
-
Ok, that answers the license question - you'll need another one. Although the size doesn't matter - you don't need unlimited on the new one if you've only got 20 users for it! Moving issues between the two is not supported yet, although Atlassian are looking at things like that as they're doing some "Enterprise" work (that…
-
I think I could do with a little explanation of the word "test" in your question. If you want a genuine "test" installation of Jira, then you can use your developer licenses to run it at no additional cost. That's for trying out stuff you want to do in your Production system before doing the changes, plugins, upgrades etc.…
-
Yes, for that, you need a "validator" that can check that someone added a work log in the screen. From memory, you'll need an add-on to provide that, I think there's one in the JIRA Suite Utilities
-
Then you have not created the new scheme. For screens, you need at least one "screen scheme" and then a new "issue type screen scheme" However, for mandatory fields, you do not need to work with screens. You need to work with "field configurations" and create a new "field configuration scheme"
-
No, it's never recommended to use javascript in description fields. There are several places you'd need to implement it (more if you have add-ons) and it's quite easy to break even if you caught every place. Atlassian have also been gradually removing the ability for javascript to be injected into fields.
-
Absolutely not. User names should be unique, or you don't know who someone is.
-
No. This isn't a Confluence thing specifically, it's an information flow thing. If you choose to let someone "access" your information, then that information is as secure as THAT person is. There's no technical fix for this. If they can read it, they can do what they want with it. It's a simple boolean concept - either…
-
In the space permissions, allow "anonymous" to browse
-
You can't really change those screens - Jira is asking you for more information that belongs to the target issue type. If you want rid of the field, then you need to remove it from the target issue type completely.
-
Yes, the choice between 2 and 3 is not one I could make for you - it depends on your expectations, process and what you want to report on. 2 really does heavily favour simple and effective planning, and tends to work better when you have short-ish sprints - the longer the sprint, the longer the defect has to wait for…
-
I've seen several approaches. * Track them separately, outside the project, so they don't affect the numbers. This doesn't really work because you have to divert project resources to deal with them, and it's * Add them as new issues. Never put them in the current sprint unless they're critical and should be classed as…
-
You could script it, but it's not going to be faster than bulk-delete. The easiest way really is "delete project", as that will just churn through all the issues, there's no limit on the number in the project. If you do delete a project, then there's some points to remember: * Deleting a project does NOT delete the…
-
It's not in administration, it's in the code - you need to hack the template file that renders the page.
-
JIRA is not written in PHP and does not implement the framework needed to support it. If you want to run PHP like that, then your best option is to install php and get it working in your web-server and not try to jam it into JIRA.
-
I don't think there is, because it's a two-layer filter - you need to run it to get the parents, then another filter to get their child issues.
-
Oh, one of those fields. Ok, we'll have to work around it. Change the board filter to: project = MC AND ( Team = 20 or issuetype in subtaskIssueTypes() )
-
In a stand-up, most look at the working board, where sub-tasks do appear. I think I should apologise for skipping over the detail in the second part of your question. Your filter is excluding them because the team does not appear to be being inherited as you think it is. So, easy quesiton - is the Team field definitely…
-
Because there is no point in them being visible in planning - you can't rank them outside the parent issue (it's of no use) and they follow their parent into and out of sprints.
-
No, customers don't have a search. If they're normal JIRA users as well, then yes, they can use it to find the underlying issues though.