I'm looking at integrating Aha! roadmaps with Jira and see you can sync:
Jira release with Aha! version
Jira Story with Aha! Feature
Jira Story with Aha! Requirement
What I am struggling with is finding a document or article on which fields are used to maintain the relatinship between the identities e.g. If a Jira release goes to sync with Aha! version which field is used to match the records so the corresponding Aha! version is updated?
Thanks for any help
Related
Our Team is Using Development tracking tools Jira for the development cycle. We extract issue details in Excel sheet and do a further activity.
Can we get data in a column of the people, who have completed development from a workflow or in other words who have Fixed issues?.
Right now, we have to open all the issue and watch manually, who have fixed the issue.
You can use the JQL:
status was "Resolved" by username
If you want to see all the issues resolved by a particular user. If you have a small team you could create a filter for each user in the team that would return the bugs they resolved.
You can also do it for a list of users:
status was "Resolved" by (username1, username2, username3)
I don't believe you can export the "resolved by" field though. An alternative would be to create a custom field called RESOLVED_BY and have the team members complete this when they resolve an issue. An even more sophisticated approach would be to automatically populate the RESOLVED_BY field when the issue is resolved.
It is also worth noting that most of the time the ASSIGNEE for a resolved issue will most likely be the person that resolved the issue.
We are planning to use one testcase management tool for our project.
I am using testlink in my previous project.
But my management want JIRA as all our sprint planning and bug tracking is happing over there.
Can I export Testlink testcases and reports in JIRA without using any add-ion
If no, Then what are other option I can use.
I have find Zephyr add-ion which can do similer like this. is it any other option present?
I have also found that JIRA can accept rest-api but then I need to make changes in testlink project so testlink can send JSON to JIRA
What should I follow. any suggestion will help
I worked with one QA team that created a custom 'testcase' issue type in JIRA. They removed all the standard JIRA fields that weren't required and added in custom fields for things that were not covered by standard JIRA fields (such as 'test category', 'pass/fail' checkbox, etc.).
The 'testcase' issues were used as sub-tasks for user stories. Using this approach each requirement had one or more test cases associated with it.
When they needed to report they would do an issue search for issues of type 'testcase' within a particular time period. Then they would export all fields to Excel.
In my company we're using Testlink and JIRA and has been proposed to remove Testlink migrating all the data to JIRA but depending of the usage of JIRA(amount of data it is managing) as this can overload JIRA due to you will need several custom fields, maybe customized with JavaScript and that can be worth.
We analysed the possibility to use the Zephyr plugin which is appropiated for this usage.
We already have set of IssueTypes and are following Agile Scrum.
Now, we're planning to use JIRA Agile. It is mentioned in JIRA Documentation that EPIC is an issue of Type "Epic". But, since we're a considerably sized BU with few projects - we would like to use the "New Feature" Issue Type as Epic - so the Spec, Dev and Test can be added to the "Feature" Epic.
Question is: Is it possible to use Custom Issue Type as Epic in JIRA Agile? If so, How?
Short answer is no.
The Epic issue type (and a few others) are added to a base JIRA installation when you install the "JIRA Agile" extension/plugin. None of the features (Epic Links, Epics filtering on backlogs, Epic burndown charts, etc) will work with any other issue type.
I'd suggest you begin adapting your process to use the new issue type.
Now, there's nothing stopping you associating custom fields (if that's what you use for Spec, Dev, and Test information) with the Epic issue type so you get the same functionality you have with New Feature.
You can rename the Epic type created by Jira Agile (note that already created schemes remember the old name) to any name and it works.
I guess, there would be hack in DB and reassign issue type to Jira Agile somewhere in DB but who knows what tables are linked to see some description here
I am transferring a jira issue to TFS WIT in my company. My team used TFS2012, they use JIRA. So I want to migrate the JIRA issues into TFS2012 WIT.
I want to preserve all the basic fields, attachments and comment history & work logging.
Any suggestions regarding tools or processes for this?
I looked into dumping the issues into an Excel spreadsheet, but that doesn't include attachments or comments.
Integration Platform
Good luck, the migration isn't usually a lot of fun.
using comment-plugins we can export comment on excel....
here we can find the comment plugins
https://confluence.atlassian.com/display/JIRA/How+to+add+comments+to+Excel+export
(we could map this to History field in TFS once we export it to Excel)
nearly 3week i worked on this task
finaly i got it
For this task we simply add USETFS plugin in jira that carry everything i mean comment tfsid and attachment everything its come under USETFS plugin in jira.
We want to create a defect/task in Jira automatically for a failed build in Bamboo. And need to assign this defect to the person who broke the build.
How to do these two things?
Thanks.
There is an open JIRA issue regarding this -- BAM-2537 -- watch it, vote for it - maybe they'll add it to the product.
The comments from Top 5 Reasons Creating JIRA Issues from Bamboo Makes Your Team Awesome-r also discuss what you're after.
Have a look at Atlassian CLI. There's already a good answer on StackOverflow.
Can Bamboo change status of tickets in JIRA
This is not "out of the box" solution, of course, and requires some additional work.