Comments
-
That looks right to me
-
It may have moved between versions, but the file name has been consistent - look for edit-textarea.vm
-
That sounds like a broken ELT to me, because the issues haven't changed. The ELT should be using a unique and immutable ID, not a component name. In fact, the correct approach here if you are using the names would be to take the "add new component, delete old one" route, otherwise you've got inconsistent data by…
-
That's why I leaned towards some form of option that lets an admin do the updates - there are no "component updated" events that could be easily caught, you'd need to hack something in to fire them, or add to the end of the rename process. (And you've got load issues, no matter how you do it)
-
You've got four options: Every time an admin changes a component name, get them to bulk-comment on every issue that has that component on it. This is a long way from ideal because it's possible to block comments, and your admins suddenly have a LOT of work to do. Amend the core code in Jira, adding something that will…
-
It's because you have not changed the issue. The name of a component really is just a name. The issue is aware that it has "component X" in the field, but when you rename it, it's still "component X", just with a different display name. So, >"respective component using issues need to updated right." has the answer "no",…
-
Pretty sure it's in 3.3, the next release, but I don't know when that will arrive.
-
You'll want a single project - if you wanted many projects, you'd need a different email address for each one. Possible, but not optimal if you have lots of clients.
-
No, it does not. There is a beta test for some connectivity, but it's very much in beta and not generally available yet.
-
Maybe. Installing JSD on your second JIRA will let you use SD functions. Then you can build your service desk in the right JIRA and you'll be able to move issues from SD projects to none-SD projects in that second JIRA. (However... bear in mind that doing that may lose the users service request information, as they can't…
-
An issue in JIRA service desk is already in JIRA - that's the point of Service Desk being an application, it sits on top of JIRA, not alongside it. That is, unless you have two JIRA installations, one with Service Desk and one without. These are separate systems, you can't just "move" from one to another, it's an…
-
Um, I'm not sure about the use of the word "move" here. JIRA Core provides us with issue tracking, with issues grouped into projects. JIRA Service Desk provides a layer on top of some of the projects that changes and adds to the interface for the project, so that customers get a simplified view and Agents have more…
-
No, this has not changed - you can't add another system fire-event.However, there are addons that provide something alongside the system event, I suspect that's what you're seeing.
-
Correct, you only get one issue updated event, for the issue you added the links to. If you added links during issue creation, then you haven't changed anything new, you've created an issue, so you get the "create issue" event.
-
I think you're over-thinking this. It's actually very simple - look at the workflow "post functions". You'll find every single one has a single, unique, non-removable function of "fire event X". You can change the X to whatever event you want. There's no "overwrite" or precedents, every action fires a single workflow…
-
You'll need to identify all the issues in the wrong status (I'd try "status was" in the advanced search), and somehow flag them to say the status is wrong. Once you've got that list, you'll need to check the workflow to work out how to transition them back to the right status. Then you can use bulk-edit to transition them…
-
Definitely need to contact the vendor.
-
Which Android Jira app is it? It's likely that the application has not kept up with the OnDemand API, but it's hard to know without knowing the app
-
Yes, a board can be created to cover as many project as you want.I would strongly recommend keeping it as simple as possible. Create a Scrum board for each team who need to plan sprints. Until you are 100% comfortable with seeing sprints from other teams leak into your boards, make sure you do not include any project in…
-
You don't choose a board. Boards do not belong to projects, and they're not issue data, so you can't just "set a field" Boards are a view on to issue data. An issue will appear on the board if the board's filter includes it. The way to get an issue to appear on a specific board is to read the filter that defines what the…
-
Yes. But they're the only options you have.You could try other approaches, but they're lossy or extremely hard work - exporting issues to CSV or other formats means you'll have to do all the project setup by hand in the target system and most formats will lose part of the data (csv won't contain history for example).
-
There's a couple of approaches here: * Create a temporary copy of your instance, delete the projects you want to hide and export the remains to xml for him * Export your production to xml, set up a temporary JIRA, import the projects you want to give to him, then export that to xml to give to him This is because there is…
-
The macro isn't customisable in that way. Even if it were, you'd need to define exactly how you tell Confluence what the status of a page is before you could use it.
-
It's not Open Source at all. Annoyingly, I can't find the licence terms, but I do know you get them if you register and ask for a (free) licence.
-
It's covered in https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens Note that a mandatory field is mandatory throughout the lifecycle of an issue. You can add "validators" to workflows that will demand the users fill in fields before progressing through a transition, but you need plugins to provide…
-
Yes, you can get one.
-
> automatically create subtasks I'm afraid you need code to do that, and you can't install the addons you need to provide that code or a place to write it. > associate with some projects I don't understand what that means. One guess would be that you want subtasks in different projects, but that's nonsense because subtasks…
-
Correct.The users who count are the ones who fall into the "can log in" group(s) - usually "jira users"
-
The second url you link to is nothing to do with customers, it's about JIRA only. Customers is a concept that only applies to Service Desk. Customers do not consume a licence
-
Login with an admin account set to work in English.