Comments
-
Not off-the-shelf. You can increase some of the class logging, but the data going into the logs is not that helpful.
-
Velocity is a measure of what you commit to in a sprint vs what you achieve. Sub-tasks are not sprint items, you don't commit to them, you commit to delivering their parents. There's an essay on how to do sub-task estimates, but the outcome is 1. They do not directly count to velocity themselves. If you do use estimates on…
-
Sub-tasks are not sprint items themselves. There's no such thing as "sub task in a sprint on its own". Sub-tasks are part of a sprint when their parent issue is in it. This is because a sub-task is part of its parent, not a separate entity. The 4 sub-tasks that are complete, great. You've got two not complete, also fine.…
-
This is recorded in the admin audit log, but there's not a huge amount of detail in it.
-
They will be whatever you set up in Crowd for the application you are creating. Crowd, like any secure system, does not store the password, it stores a hash to validate against. If you don't know what was set, you'll have to reset it.…
-
It's the line def cFieldValueLinkEpica = issue.getCustomFieldValue(cFieldLinkEpica).toString() throwing com.atlassian.jira.issue.fields.ImmutableCustomField cannot be cast to java.lang.String Epic Link fields do not contain strings. You'll need to read the API Docs to find out how to get what you want out of it.
-
Ok, well, most, if not all of us here have any knowledge of your particular Jira installation. We're a community of people here to talk about Atlassian, and whilst some of your users or admins might be here, most, if not all of us, will have no knowledge of your particular Jira installation. I think you've clicked on "help…
-
This suggests you have an automation or script changing components on your issues dependent on the Epic Link. Jira Software does not do this off-the-shelf, it has to be added. Check with your admins for automations and listeners that might be doing it.
-
Yep, it's a quirk of the lexorank system, which can happen when an issue and the issues around it have been repeatedly re-ranked in a similar area. It's a bit more complex than this but you could say "it's run out of gaps to move things into". It can also happen if the database or index get damaged by something (frankly,…
-
You do not. You have no access to the database behind your Cloud system. There are some apps that export a lot of data from Cloud and can push it into another database, and there are plenty of reporting apps in the marketplace, and there is also a "data lake" in early access, but you'll not get direct SQL access to Cloud.
-
No, there's no way to block access to specific reports by person or group.
-
Not directly. The point of a transition screen is to ask the user to fill in or update fields. So if you put a field on it, it will be in edit mode. I don't think there's a way to do this with read-only or scripted fields either - they don't appear on transition screens because they're not editable. The closest I think you…
-
No, the UI doesn't support arbitrary pop-ups (because people hate them. You'd find if you forced this, people will give you a junk reason most of the time). A transition screen is the way to do this - even though it's still a pop-up, it actually makes sense to people and doesn't irritate them because you're offering them…
-
I think Advanced Roadmaps provides the ability to implement this sort of thing, it's just one way to look at sets of team's work and have an overall plan for them. I'd look at https://www.atlassian.com/software/jira/guides/roadmaps/advanced-roadmaps
-
Most of us don't do that, you might want to think about engaging a partner or consultant, or talking directly to Glidr instead of an Atlassian place - most of us probably can't help you with Glidr. (Also, most of us will start with the question "what are you trying to do, and what have you tried from the Glidr docs?")
-
The id is exposed in a few places. The two I usually go for are: Make a REST call to Jira asking for the metadata for "create issue" in a project that uses the field and has it on the "create" screen Go to Admin -> Issues -> Custom fields, and find your field. Hover the cursor over the edit or configure links on the right,…
-
No, the space permissions are at the top of the permission tree and cascade down. To let someone have access to a page lower down, they have to have access to the space.
-
Ok. And are they managed? I mean, have you claimed the domain of their email addresses so you can manage them globally?
-
Ok, then what are you looking for?
-
There's a good starting point at https://developer.atlassian.com
-
I am sorry, that does not answer the question. Are they Atlassian accounts? Atlassian Access in use? Google Accounts?
-
I am not clear on what you are looking for here. Status has nothing to do with field, and I'm not sure what you mean by "tag"? Do you mean the id of a field, so you can use it in a remote automation? What has status got to do with it?
-
What type of accounts are you using? Atlassian accounts (managed or not?), Google or something with Atlassian Access?
-
Jira's JQL does not have "field 1 = field 2" operators, they're all "field 1 has <value>" type clauses. To find out if two issues have the same value, you have to read through the results of "field = X" to find out if both issues are on the list. But you can easily copy field values from one issue to another - have a look…
-
That is what the global rank field is for! If people re-rank inside their projects, you need to know that on a more global level. I think what you're really looking for is a way to prioritise based on something other than the actual rank.
-
You cannot change field types. On Server, there's a database hack you can use, but you don't have database access on Cloud. Your only option is to create a new field, and then use bulk-edit to populate it for existing issues.
-
You will need to read the application log to find out what is going wrong with the installation. It should be being logged in <jira home>/log/atlassian-jira.log
-
Yes, the query does not mention status. I think you'll find all the missing issues have a resolution set (the "resolution = unresolved" really does mean "resolution field in the database is empty") Could you check one of the missing ones and its resolution in the issue navigator? What exactly is it showing for the…
-
Follow the new "wizard" through with whatever is closest to what you need, but make sure you select a "company managed" project type. Then select "Share settings with an existing project" and you can tell it what project you want to "copy" It's not quite a copy - new schemes for config are not created, just shared, so if…
-
Could you explain what myRcl and ctrac are, and what they have to do with Jira? (or any Atlassian thing)