Comments
-
The display skips some days markers when the text would make it hard to read (mostly when it would overlap other markers). You can't change this (and wouldn't want to, as it would make your charts harder to read)
-
"parent = MDC-27" Should return values for "I have an issue MDC-27 which has a child issue of MDC-76.", including MDC-76 If this is not working then I would want to question your definition of "child issue" - do you really mean parent/child (better explained by the Jira-speak issue/sub-task description) or are you looking…
-
These are transitions you have chosen to make available to the customers. You should be able to remove them by removing the "customer can trigger this" option from the workflows.
-
Jira has no function that "creates an issue matching current filters". I think your old Jira was simply set up to default fields on create to things that happened to match the filter. In your new Jira, it's not setting those things automatically.
-
As before - You do not need to make a workflow active directly or "publish" it, the active/inactive display is not a flag, it is simply an indicator of whether the workflow is in use or not. Associate it with a project (via a workflow scheme) and the indicator will change to active.
-
Epics are a separate thing again - they are a layer above issues (stories). They are not expected to go into sprints, they're expected to act as a grouping of many issues (that do go through sprints), ending when all their component stories are finished. So, yes, you can (and should) handle Epics separately, and outside…
-
You can use anything with a schedule to do things in Jira by setting them up to hit the REST API to do what you need. (I tend to write scripted services inside Jira as they run on a cron expression, but there's nothing wrong with doing it externally over REST)
-
It is more simple in Confluence, because there is only one application (Jira has three, licenced separately and jointly - a licence for Software or Service Management effectively includes a Core licence too) A person consumes a licence if they can log into Confluence. Admin, confluence user, any other group that has the…
-
Select list fields store options you select, not numbers, so you can't just add them up. You will need to read the value of each field and convert from an option to a number (bearing in mind one of your admins could easily add something like "three" or "twelvety" as options, so you'll need to catch non-numbers), then add…
-
You'll need to find or write an app to provide that. I'm not aware of any that have the simplistic approach of setting an expiration date, mostly apps looking at old content are more about monitoring usage to establish pages (not spaces) that are less used and giving you archiving options.
-
There's no way to arbitrarily drop numeric fields from that list - the whole point of the selection is that it can use any number field.
-
Queues are not containers, they are much like boards in that they select for a range of issues. You can't "move" an issue between queues, you have to change the issue in such a way that it stops matching the selection criteria for the queue you want to get it out of, and make it match the queue you want it in. So look at…
-
No, you will need to make the whole project public. If you then want to hide issues from public view in that project, you can use issue security to hide them.
-
"Integrated" - no. That's a word that really has no meaning. This is not something we can directly answer. Yes, you can export from Service Now and import stuff into Confluence. All our computers can talk to each other properly nowadays. I think the more important question is about what you want to share? Could you explain…
-
Mixing and matching "or" with "and" confuses humans very easily. You have to try to think about how the computer is reading it, and we don't instinctively see it the same way as them. The answer with mixed and/or searches is almost always parentheses. It's the grammar of searches to computers. If you break down your query…
-
Absolutely - ask the people around you what is working well and get involved with them!
-
I can't give you a better update than @Vicknesh Shanmugam has
-
p.s. use the Key, that's the one that you need to think about.
-
You can ignore the "UID", it means "unique identifier", which in Jira, is a description of both the issue "key" and the issue's ID in the database, it's not a separate thing from those two. Unless it is being mixed up with "UUID", which is a "universally unique identifier". There's an essay here, but it's probably not of…
-
What do you mean by "hidden webfragments"? Could you explain what you are looking for here (also, what has the app got to do with it and what actually is the app?)
-
You can't update the database on a Confluence that is active, it will break and corrupt your data. The best you can do with a spreadsheet editor is probably the Office connector app, which at least handles the download/upload bit more smoothly.
-
I think you might need to expand on that. You seem to be assuming that Confluence spaces have an expiration date (they do not), so you'll need to explain what you are using to implement it first.
-
Slight argument on that - sliced garlic, crushed/minced garlic, whole cloves and half and half (slice it then crush it a bit with the flat of the knife) all add different flavours to a dish.
-
It's the same answer as given above
-
No, there's no way to do this. Sub-tasks are not independent items, they aren't even items you can commit to in a sprint. They only become part of a sprint by virtue of being a part of an issue that does go into it. If you want to handle them separately to thing of which they are a part, you can convert them to issues…
-
There is no "standard plan" for self-hosting, see https://www.atlassian.com/software/jira/pricing?tab=data-center for the tiers of pricing you have available, and https://confluence.atlassian.com/enterprise/node-sizing-overview-for-atlassian-data-center-941612709.html to help size the sort of kit you will need to run it on.
-
If you can search for it with JQL in Cloud, then that means the field is fully functional and should be available in search and REST automatically. I think we need to delve into the exact configuration of the field. What does it look like (what's its "type") when you look at the list of custom fields? What is the script…
-
There's no simple answer to that, the best we can do is probably "your team and thier leads need to talk to the rest of your organisation"
-
You would need to restore a backup to get the user's dashboards back. Deletion deletes everything, there's no records in the database any more.
-
These are my three oldest surviving items of swag from the ecosystem. Not entirely representative though: * I think my dragonslayer shirt was older than the "issues" shirt, but it was too well worn/loved/battered and went to be recycled a long time ago. T-shirts only have 4 holes, 2 arms, a neck and a beer-belly, right?…