How might you architect this?
We typically have about 20 active job-sites with 20 to 100 persons assigned to each job-site. Jobs last from weeks to years, and as a job ramps up/down the manpower requirements change. Sometimes an employee simply wants to request a new assignment due to personal issues, or location. Sometimes the job assignments come from the site Superintendent or administratively from the region General Superintendent.
Currently the General Superintendent keeps a Kanban type board up in his office whereon each "Card" is a person's name, title. Some specific skills are iconized with colored dots; org structure hierarchy (Apprentice, Journeyman, Foreman, Superintendent, etc) determines the card background color.
I'm would really like to build a JIRA Kanban board with similar features, but I'm struggling with the architecture. In this model each Person maps to an Issue. Title, Skills map to custom fields. Title is a Single Select Option. To color the cards may be possible with ScriptRunner or some such. Job-Site however would be a Status in a Workflow.
We would need to use the API to create and update each person, skills, title, and job assignments. We would need to create a new workflow every time a Job-Site was added or removed, and then assign that new workflow to the project, and remove the previous workflow.
What other complications do you think this might idea might experience in implementation?
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs