Couple of queries:
1.)
I have a Sharepoint with multiple columns of data(say some 8 columns of Text and numeric values).
Now, there is a need to transform this data into JIRA tix capturing all the 8 columns values as well ..
i know a manual way of doing it which takes time .. hence, checking with you to see ..if any more advanced or optimised way of doing this ?? please let me know ..
2.)
need to calculate and track the Capacity plan of those JIRA Tix (which engineer is occupied with how many stories/epics and what is the remaining capacity available etc) once the above question is accomplished ..
now, im aware of capturing Story points for stories and calculate it .. however, the main ask is 'How to do this for EPICs ? ' .. considering that EPICs dont have an option of Story points concept, how to do this capacity tracker for EPICs in CONFLUENCE ??
please help
Hi Ramu,
Sharepoint is a a place to manage files online. Are you referring to like an excel document? If not, what is the file format? Depending on the format, there maybe market place tools you can use. otherwise, if supported on Jira, you can use CSV importer.
See below:
https://support.atlassian.com/jira-software-cloud/docs/create-issues-using-the-csv-importer/
You can add time tracking or story points to Epic. However, there is no sum up from stories to Epics, you will need to look into automation or marketplace apps.
You can connect Jira and Confluence together and show Epics. Confluence is not a capacity planning tool. Jira would be the right tool for this since that data is there. Confluence would best be used to provide context around Jira data to help audience understand the data.
-Ben
Thank you @Lukas Maczejka - JXL and @Benjamin
for the 1st query:
Im aware of the csv importer option and i have admin rights to that where i can being all the csv content(stories/epics in this case) into JIRA Tix
what i missed was that thought for a second that i can export the Sharepoint data into csv (somehow it dint flash the moment i was asking this query) ..
will give a try .. Thanks
2nd query:
Once i have the JIRA Tix created capturing the Story points .. i use Confluence Table to display a snap view of the Users, Utilised Story points and remaining Story points .. i do it via Table transformer as it covers few arithmetic calculations as well
anyway im happy and glad to know that EPICs can have the Story points as well once configured which is a news to me ..
Will try this as well .. Thanks again for the valid inputs .. :)
@Lukas Maczejka - JXL -> reg: custom fields import from csv one ... say that i have done it but then .. will my jql reads those cutom fields as valid ones when i try to query something on this in future ..
for example, if i create a custom field (which also i configure in my project), if i try a JQL .. assignee = user1 and statuscategory != Done and custom field = xyz .. will this query works for custom field .. !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ramu,
1. Importing SharePoint data into Jira
As @Benjamin mentioned, the CSV importer is the way to go. The steps:
One thing to keep in mind: this requires site or org admin access. If you're not an admin, you'll need to coordinate with one.
2. Story points on epics and capacity tracking
You can actually add story points to epics in Jira Cloud. The Story Point Estimate field is available on all issue types, including epics. You may just need to add it to the epic's issue layout if it's not visible yet.
The bigger challenge is what you're really after: automatically summing up story points from child stories to their parent epic. Jira doesn't do this natively. Some teams use Jira Automation to recalculate the epic's story points whenever a child changes, but that can get complex to maintain.
If you're open to using an app from the Atlassian Marketplace, JXL for Jira can help especially with part 2.
JXL's sum-ups feature automatically aggregates story points from child stories up to epics, with no automation rules to maintain. You can also group by assignee to see each engineer's workload across their stories and epics. And once the issues are in Jira (via CSV import or otherwise), JXL's spreadsheet view lets you bulk-edit field values across hundreds of cells using copy-paste from Excel, which can speed up any cleanup after import:
Disclosure: I work for the team that builds JXL.
Cheers, Lukas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.