Comments
-
What do you mean by "raw"? The data in the database?
-
Yes, that's pretty much what I say about a lot of Microsoft Software.
-
The best option is to use REST - it doesn't change much, when it does change, the changes are usually "make more stuff available" and it's available off-the-shelf.But does Power BI support that? At a guess, it'll probably demand access to the database, which is a nightmare because you'll need to build and maintain data…
-
How do you plan to connect it it? What's the method for "pull"?
-
Well, I knew that really, but my point is more about what you want from it, and how you propose to connect it to JIRA.
-
Depends - can it talk to JIRA over REST? What does it do, and what do you want from it?
-
https://developer.atlassian.com/display/JIRADEV/JIRA+REST+API+Example+-+Query+issues Replace "assignee=fred" with "project=XYZ"
-
Imran, no. The original question was not valid. The answers given to it answered it. Once we got an explanation of what the actual question was, then yes, that was perfectly valid. But we did not know that until later. The reasons for needing a range search are also unclear, but that's just me being curious, as I can't…
-
Imran, it's a perfectly valid question (once we worked out what it really was), and well worth asking, as it's not particularly obvious from the UI or the documentation. My follow-on question was more about the human side. I've never come across anyone ask for a range of issues like that. I can't actually work out any…
-
Areik, it is a good place. We're trying to help. We didn't understand your actual question at first because it was not clear - it pointed at project key, and did not mention the "sequence range". I'm still not entirely sure that "a range of keys" is useful in human terms, but if you think it's useful, I don't know your…
-
I think it's because you didn't really ask a useful question at the beginning. Your original post was phrased as "how do I search for an issue by it's project key", which is pretty much basic in Jira and you didn't explain what you were really asking.
-
We have given you an accurate answer to the question you asked. It's not our fault if you ignore the responses. It actually turns out that you had failed to explain your question properly. If I have understood your more recent explanation, your question is NOT "I want to search by issue key". It is "I have a project and I…
-
No, sorry, you don't have to use JQL, I just use it because a lot of searches that come up as questions are only answerable in JQL. The simple search lets you select project as well.
-
I'm afraid you're missing my point. "I want to search on project key" - great, all issues belong to a project. Each project has a unique key. So you type "project = X" into the advanced search and you get a list of issues in the project. I think the problem is you are not explaining what you mean by "search on project key"…
-
I'm not quite sure that there is a question here at all. When you build a filter, the JQL ends up with a clause of "Project = MyProject". (The simple search interface names project as a valid field, and ends up generating that JQL in the background). So I'm a bit lost on why you're talking about custom search filters or…
-
It's the resolution. You need to set that in your workflow as you go into a complete status, and clear it as you leave. "Resolution determines open/closed" is a bit of a bodge in my humble opinion - it made sense in Jira 1, but as things have moved on (configurable workflows, Jira Agile and now Service Desk) it's become…
-
Ah, ok, that's really helpful for my understanding. I think I get it all now, you haven't implemented a new system, just misunderstood the existing one. But I don't know what you mean by "with our custom status there is no way to mark it as completed". You set the "complete" category on that status, and ensure that all…
-
Sorry, you are missing the point. You've said that you've created your own status system - that's pointless because Jira still uses a workflow, and it is far easier to design your own workflows. You might as well use the built in stuff because it already handles what you need and it's far easier than bodging in some…
-
It won't happen. Why on earth have you done this? Why don't you just create your own workflows?
-
This sounds very confused - you're asking about close/resolve not showing, but then say you have a transition that changes the category. What category? Transitions change status, not category? The only thing I can think of is that it sounds like you implemented your own status system using category instead of status, which…
-
Do you have a close/resolve transition in the workflow at all? If you do have it, then check the conditions on it. The permissions helper should be right in theory, but if it's telling you this should be working and you definitely don't get the options, you should check it all from the basics.
-
Not without add-ons of some sort. A page has content, such as text and macros. If a user can edit pages, they can edit the content, that's what it's for. Attachments and questions are separate permissions
-
Possibly, depending on when you want this "lock" to occur. You can remove the field from the "edit" screen, but that removes any ability change the field in general - your users will only be able to change it during transitions. Editing (and creating) comments is unrelated to screens (have a look at the permission scheme…
-
What do you mean by "get", and "email request defined for a project"?
-
There's no particular version of JIRA that matters for importing data from there. You mention "Agile", so I'd recommend JIRA Software over plain JIRA, and I'd quite simply say the latest version. You are talking about test cases and defects. That's fine, but you need to think about how you are going to represent and use…
-
I don't think you have understood how these things work together. A post function is something that happens in a workflow. You move from one status to another through a transition, and the post-function runs during that transition. Post-functions have nothing to do with screens An "issue type screen scheme" tells your…
-
Most of this goes back to defining what some of what you've said really means. "A user's sub-tasks" - how do we know that they "have" the task? This goes into your second question - "to which the user has a relation". In all of these, how are you telling JIRA who the sub tasks and stories "belong" to?
-
The permission scheme requires the field to be searchable otherwise it will not work. If it can't search the field, it can't know who can see the issue. If you want to make the field unsearchable, you will need to remove it from the permission scheme, then you'll be able to remove the searcher from it.
-
You'll want to use the REST APIs to talk to JIRA. I often point at the documentation for those, but the examples and tutorials are often more useful - https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials - and they're part of the doc tree, so you can get to the other stuff quickly from…
-
You'll need to find or write some code for this: you need a condition to control when someone can start the transition based on the component, and then a post-function to pick up the test manager and put them in as the assignee.