Comments
-
There is no way to add more categories, the three are hard-coded (and allow for empty)
-
Jira has a core principle that there is one single assignee so there can never be any confusion. Atlassian have no plans to change that. If you want to represent both people in a pair, add a field for the other person.
-
You will find your second "Epic" type does not work the same way as the main Epic type. Jira Software expects there to be a single Epic type and simply won't recognise a second type. So there's no real "impact" beyond "it won't be treated as an Epic" And, don't unlock the fields, they're locked to stop you breaking things.
-
The integrity check has to be run while Jira is up - it's run as part of the system! It does not have a significant impact on the users, although it does consume some resources while it runs. For a large Jira, I would avoid running it during the more active times, and out-of-hours if possible, but it won't cripple it.
-
Could you explain what the "belongs to feature" thing is? A field you've added? A link in Jira? Something added by an App? A sub-task?
-
Check that the app is installed and enabled from Admin -> Manage add-ons What documentation is telling you to look in global permissions?
-
>Was this changed in the recent releases? No, it has not changed since Jira 1 >Is there some other table which I could join to my query to retrieve details related to date and time both? No, because, as I said before, the data is stored in the tables you are reading, and there is no reason to duplicate it elsewhere. The…
-
If you use the Jira Service Desk installer to do the baseline install as part of your script, yes, it will install both.
-
You don't. The portal lists all possible request types.
-
No, Epics are expected and intended to go across projects, and the software is built to cater for it.
-
Go to the board, click configure, go to the estimation tab, change the field selected for estimation.
-
There's a (rather non-intuitive) clue on the line above. This board is using a simplified workflow, which allows board admins to add columns, and status to columns, and also allows project admins to add status to the workflow. But note that a board admin is not necessarily a project admin, and vice-versa. I think you have…
-
If you do decide to do this with a script, you will need to think of several things. Field A + Field B + Field C is fine, but your autoincrement will need a place to store "last used" and you'll need to think about how it handles when a couple of people create an issue very close together. And bear in mind the string is…
-
If you change the board to use Estimates instead of Story Points, the Sprint Report will follow.
-
That's fine - Jira only limits the total number of agents (to your licence level). It does not care if you have 1 agent in project 1 and 399 in project 2!
-
No, the pie chart is hard coded to report the number of issues in the groups.
-
The "go into a sort of read-only mode" is the same, yes. No data loss, no locking out, just "can't write issue/page data" The applications synchronise an internal copy of the user and groups lists when they synchronise from any remote user directory. So they "know" what users are in a group because they've asked.
-
Don't try to rename "Issues", it's just going to confuse people. It would be better to set up your own "issue type schemes" - ones that include Action Items and Requirements as issue types (and then remove the default "issue" issue type from them)
-
Yep. Reading it is a bit of a nightmare, and you absolutely can't write. If you explained why you are asking, there's a very good chance someone here can give you a much better way to achieve your goal.
-
How are you storing/representing these test scripts? An App for Jira Cloud? Just as Jira issues? An external system?
-
You can use plain Jira Core to do this, but things will be very open to your customers, and you won't get (without a lot of customisation) the reports and measurements that most people would like from a Help Desk. I would strongly recommend a look a Jira Service Desk instead of just Jira Core - this separates customers,…
-
The most simple one is to use the "include" macro to pull the whole "original page" in as a section in the second page. A variation on that is to use "excerpt-include" to draw in only part of the page. In both cases, you have a single source of information on one page which is then displayed as though it is part of any…
-
Either * the screen is not associated with your project and issue type * the fields do not have the right context * the fields are hidden in the field configuration * the person using it has not got them selected The simple solution - click "configure fields" to the top right of the popped up screen. There's a "where's my…
-
See https://confluence.atlassian.com/kb/securing-your-atlassian-applications-with-apache-using-ssl-838284349.html - it is for Apache proxy servers specifically, but the stuff about the Tomcat connector applies for most proxies and load balancers. Check the section "configure the atlassian application / update the connector…
-
Ah, I see. Direct and "watching", not "pending". Direct notifications are generated by actions that are directly because you are named - @mentions, being the assignee of something. Pending are the others, things you're getting because you are part of a group or role named to get those events.
-
5,000 on Cloud, unlimited on Server and Data Centre. See https://www.atlassian.com/software/jira/service-desk/pricing?tab=self-managed (there's a flip to Cloud on there somewhere)
-
I'd say this is poorly phrased in the doc, but I am not sure how to improve it clearly or without writing an essay. My instinct is to say "use your common sense" - if someone cannot see an issue, then they should not be able to edit it, log work on it, link to it, reschedule it and so-on. I think that's probably all you…
-
You do need to have fields that are of the same type for most "copy value" functions to work. We don't know which one you might be talking about - there are a lot of Apps that have this function in them. Most are very simple and can only copy between fields that hold the same type of data, but some will try some more…
-
No, you're either a System admin or you are not, there's no sharing of bits of it. Although Atlassian are working on better delegation.
-
You can add the rank field to displays, but it won't mean much to a human.